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

Annotations cover only readOnlyHint and openWorldHint, and the description layers on substantial extra behavior: it is paid ($0.005), deterministic, no AI, nothing stored, body capped at 1000 KB, failed 4xx/5xx calls are not settled, and a missing payment header returns x402 payment requirements. This is exactly the payment/settlement context an agent cannot get from structured fields.

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?

Front-loaded with price and purpose, then format support and output contract in dense, information-bearing sentences. Slightly overloaded by packing payment/settlement mechanics into the same block, but little is wasted.

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?

No output schema exists, so the description carries the return-value burden and does so fully (accounts, balances, signed transactions, ISO dates, counterparty, reference, OCR number). Combined with the error/payment behavior, an agent has everything needed to call it correctly.

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 100%, so the schema already documents all eight parameters, establishing the baseline of 3. The description adds only indirect meaning (the format list maps to the format enum and the output fields hint at CSV column mapping); it does not clarify columns, delimiter, decimal, or dateFormat beyond the schema.

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?

States a specific verb (parses) and resource (bank statement) plus the output shape (normalized JSON with accounts, balances, signed transactions). The supported input formats are enumerated precisely. It does not differentiate itself from siblings like convert_statement or analyze_statement, so it stops short of a 5.

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?

Usage is only implied: it discloses the $0.005 cost and the x402 payment-header precondition, but never says when to choose this over analyze_statement or convert_statement. No exclusions or alternative-routing guidance is given.

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