Reconcile Currency Rounding

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

Annotations already provide readOnlyHint=false, idempotentHint=true, etc. The description adds critical behavioral context: dry run by default, execute=true applies fixes, and thresholds (<0.10 EUR or FX journals for 0.10-1.00 EUR). No contradictions with 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?

Two sentences cover purpose, dry run behavior, thresholds, and execute flag. No wasted words; front-loaded with key information.

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 the core behavior, thresholds, and execution mode. Missing explicit output description (no output schema), but the dry run output is implied. Context signals (5 params, no required) are well-covered.

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 schema already documents all 5 parameters clearly. The tool description adds minimal extra meaning beyond referencing 'execute=true'. Baseline of 3 is appropriate.

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 tool reconciles small PARTIALLY_PAID purchase-invoice currency residuals, specifying the verb 'reconcile' and the exact resource. It distinguishes itself from siblings like reconcile_bank_transactions by targeting currency rounding residuals, and mentions dry run vs actual execution with specific thresholds.

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 small currency residuals on partially paid purchase invoices) and the dry run default with execute=true for applying fixes. It does not explicitly exclude alternative tools or provide when-not-to-use guidance, but the scope is clear enough for an agent to decide.

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