list_bank_transactions

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

The description adds context beyond annotations by clarifying these are not live bank feeds and explaining status represents reconciliation status, not journal creation. This complements the readOnlyHint and openWorldHint 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 four sentences, efficiently conveying purpose and key distinctions without unnecessary words. Each sentence adds value.

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?

While explaining data nature, the description omits pagination, sorting, and filtering details. For a list tool with 8 parameters, more completeness is expected despite good annotations.

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?

With schema description coverage at 50%, the description does not add meaning for parameters like status, sort_column, page, or per_page. It relies on schema enums but lacks explanation of values or usage guidance.

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 'List bank transactions in Zoho Books', specifies they are for bank reconciliation, and distinguishes from live bank feeds. This differentiates from sibling tools like categorize_bank_transaction_* and list_account_transactions.

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?

The description implies the tool is for listing transactions for reconciliation but does not explicitly state when to use it versus alternatives like list_account_transactions or match_bank_transaction. No 'when to use' or 'when not to use' guidance is provided.

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