match_bank_transaction

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

Annotations indicate a write operation (readOnlyHint=false) and openWorldHint=true. The description adds that the tool updates bank reconciliation status, providing behavioral context beyond annotations. No contradictions.

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 sentences, each serving a distinct purpose: main action, prerequisite hint, and behavioral note. No unnecessary words, well-structured and front-loaded.

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 tool's complexity (array parameter with required subfields), the description provides enough context: prerequisite tool, effect on reconciliation status, and a common misunderstanding. No output schema is present, but the description sufficiently conveys the action's impact.

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 baseline is 3. The description does not add meaningful details about each parameter beyond what the schema already provides. It mentions 'one or more' existing transactions, but this is implicit in the schema's minItems:1.

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 action 'Match' and the resource 'uncategorized bank transaction to one or more existing Zoho transactions'. It distinguishes from sibling tools like categorize_bank_transaction_* and unmatch_bank_transaction, and mentions a prerequisite tool.

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 explicitly advises to use get_bank_transaction_matches first to inspect candidates. It also warns that creating a journal alone does not mark imported bank transactions as matched, guiding correct usage. It lacks explicit when-not-to-use but provides strong contextual cues.

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