Reconcile Inter-Account Transfers

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

The description explains the duplicate-safe behavior (skipping already journalized transfers) and the dry-run mechanism, adding context beyond annotations. The destructiveHint annotation aligns with the described confirms/deletes.

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?

Three concise sentences, front-loaded with purpose, using emphasis for key terms. Every 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?

The description explains the return value for dry run and the execution flow. It could be more precise about the plan contents, but it is reasonably complete for a tool with 4 parameters and no output schema.

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 100% schema coverage, the description adds meaning by explaining the dry-run workflow (plan_handle) and special use of target_accounts_dimensions_id, going beyond the 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 the verb 'match' and specifies the resource 'own-account bank transfers', distinguishing it from sibling reconciliation tools like reconcile_bank_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?

It provides clear usage guidance on dry run vs. execute, the requirement for plan_handle when executing, and when to pass target_accounts_dimensions_id. However, it does not explicitly contrast with alternative tools.

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