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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing cost ($0.01), settlement behavior (4xx/5xx not settled), the x402 payment-requirements response when no header is present, and a 1000 KB body limit. These are exactly the operational facts an agent needs to invoke a paid tool safely.

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?

Effectively one dense paragraph that leads with the paid nature and then the payload/behavior facts; every clause carries information. Slightly crowded, but nothing is redundant filler.

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?

For a 10-parameter tool with no output schema, the description covers the payment lifecycle, what the analysis contains, the size limit, the analysis-only toggle, and the no-payment fallback. Combined with the fully documented schema, 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 description coverage is 100%, so the schema already carries most parameter meaning (baseline 3). The description still adds value by clarifying include_transactions=false yields analysis-only output and by stating the 1000 KB body constraint, which is not expressed in 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+resource ('parses a statement and adds analysis') and then enumerates the concrete analysis outputs (monthly totals, top counterparties, recurring payments, duplicates, largest transactions, balance reconciliation). This clearly separates it from siblings like parse_statement or convert_statement, which produce no analytics.

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?

Gives clear operational context for the paid flow, including how to get analysis-only output via include_transactions=false and what happens without a payment header. It does not explicitly name a sibling or state when to prefer this over parse_statement, so it stops short of full when/when-not routing.

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