Reconcile Inter-Account Transfers

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

Beyond annotations (destructiveHint=true), the description discloses that it skips already journalized transfers (duplicate-safe) and defaults to dry run. This adds valuable behavioral context beyond what annotations provide.

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 short and front-loaded with the core purpose. Each sentence adds distinct information without fluff. Highly efficient.

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?

The description covers key behaviors (duplicate-safety, dry run) and an edge case, but lacks a clear explanation of the matching algorithm (e.g., how transfers are paired). Given the tool's complexity, this omission leaves some ambiguity.

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 baseline is 3. The description adds value by explaining the execute parameter's effect (dry run vs confirm) and the condition for target_accounts_dimensions_id, slightly expanding on schema descriptions.

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 'Match own-account bank transfers' with a specific verb and resource. It distinguishes itself from siblings like 'reconcile_bank_transactions' by focusing on inter-account transfers.

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 explains when to use the tool (for own-account transfers) and provides context for the dry run mode and duplicate safety. It also mentions a specific scenario for the optional parameter, but does not explicitly compare with alternatives.

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