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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the requirement for date, description, and amount columns (or debit+credit), which is valuable behavioral information beyond the schema and annotations. It does not contradict any annotations.

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?

The description is three concise sentences, each adding value: the core purpose, the required columns, and a related workflow pairing. It is front-loaded and free of 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?

Given the output schema exists and the tool has straightforward parameters, the description covers the essential aspects: purpose, input requirements, and workflow context. The agent has enough information to select and invoke this tool 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% for all five parameters. The description adds meaning by specifying the required CSV columns, which are not detailed in the parameter descriptions. This goes beyond the schema and helps the agent understand the tool's input constraints.

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?

The description clearly states the verb 'Convert' and the resource 'transaction CSV' to produce a '.qbo / OFX bank-feed file' for QuickBooks. This is distinct from sibling tools like csv_to_json or csv_to_chart, as it is explicitly for accounting software imports.

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?

It provides clear context about when to use this tool: to create a bank-feed file for accounting software. It also mentions a complementary tool 'extract_statement' for a statement PDF workflow. However, it does not explicitly say when not to use it or mention alternatives like other CSV converters, so it earns a 4 rather than a 5.

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