Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present the description carries the burden, and it does disclose a material trait beyond schema: this is a paid call requiring $0.40 USDC via x402. However, it says nothing about payment/auth flow, failure modes, latency, or whether the charge is incurred on error, which matters for a paid tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with the core capability front-loaded and the cost appended, no filler. The metric abbreviations (MCA, DSCR) are jargon-heavy but appropriate for the domain, so the compression is earned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description enumerates return contents, which partly substitutes for the missing output schema, but for a paid financial extraction tool it omits the payment/auth mechanics, error and retry behavior, and how the three input parameters combine. Adequate to know what it does, thin for calling it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 67% and the description adds no parameter meaning at all. Critically it never clarifies the `type` enum relative to this specialized tool (must the caller pass type=bank_statement, or is it forced?), nor that url and file_base64 are alternative input modes with zero required parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Names the resource (bank statement) and enumerates the specific outputs (transactions, ADB, NSF, MCA/loan positions, DSCR inputs, tamper flags), which is far more specific than a generic extraction tool. It never mentions the siblings extract_document or preview_document, so an agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this rather than extract_document or preview_document, and no prerequisites or exclusions. The only usage-adjacent signal is the price, which hints at a cost trade-off but gives no routing rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.