Financial Synthesis Tool-Calling Pre-Deployment Verification

Role: Senior Automation Consultant specializing in enterprise ERP data pipelines and LLM tooling.

Context

• Advisory practice tier: {{consulting_firm_tier}}
• Target ERP platform: {{client_erp_system}}
• Exposed tool endpoints: {{query_tool_endpoints}}
• Per-query execution cost cap: {{maximum_cost_budget}}
• Client data scrubbing standard: {{data_sanitization_rules}}
• Response latency threshold: {{latency_sla}}

Task

Generate a pre-deployment verification checklist for automated analytical tool calls executing financial queries and data synthesis against client enterprise databases.

Method

1. Analyze function descriptions across {{query_tool_endpoints}} for semantic overlap and ambiguity.
2. Verify strict read-only enforcement across all database querying function definitions in {{client_erp_system}}.
3. Validate argument sanitization routines against {{data_sanitization_rules}} to prevent financial record leakage.
4. Check response payload serialization to guarantee adherence to {{latency_sla}} limits.
5. Audit recursive function calling limits and token overhead to protect {{maximum_cost_budget}}.
6. Review parameter schema constraints for currency formats, fiscal date ranges, and ledger codes.
7. Test agent tool-selection accuracy against edge-case queries and negative prompts.

Constraints

• MUST restrict all database-facing tool calls to idempotent, read-only operations.
• MUST NOT allow function schemas with unconstrained string inputs for financial ledger identifiers.
• Checklist items must include explicit verification commands or automated test criteria.
• Total checklist items across all sections must not exceed 15 points.

Output format

• Section 1: Schema Integrity & Tool Selection Checklist (5 items)
• Section 2: Data Sanitization & Read-Only Safety Checklist (4 items)
• Section 3: Cost, Token & Latency Budget Checklist (4 items)

Self-review

• Check that all 6 variables are referenced in context and method steps.
• Ensure each item specifies an exact verification command or measurable outcome.
• Confirm no write or mutation functions are permitted under any circumstance.