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

Annotations already establish readOnly/non-destructive/closed-world, and the description adds real behavioral context beyond them: exact-decimal arithmetic, that missing costs 'stay unknown' (null handling), that declared totals can be cross-checked, and that no key/credits/wallet are required. It still does not explain the non-idempotent behavior hinted by idempotentHint=false.

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?

Front-loaded with the core purpose, which is good, but 'FREE during validation' and 'No key, credits, wallet or preparation needed' are redundant, and 'Supply your task in input' / 'Existing source and input limits apply' are filler.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What remains missing is usage guidance and semantics for the required nested fields, leaving the definition adequate but short of complete for a complex nested-input tool.

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 0% and nested fields are undocumented, so the description must carry the load. It does surface the key components (items, discount, shipping, tax, fees) and the declared-total check, but leaves required fields like currency, minorUnitDigits, quantity, and unitPrice unexplained.

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?

Names a specific verb ('Reconcile') and enumerates the resource components (item, discount, shipping, tax, fee amounts), which distinguishes it from siblings like commerce_money_parse and commerce_unit_price. The purpose is legible, though 'reconcile' is somewhat abstract and it never explicitly contrasts itself with those siblings.

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?

There is no when-to-use guidance and no mention of alternatives such as commerce_unit_price or commerce_money_parse. 'Supply your task in input' and 'Existing source and input limits apply' convey nothing about selecting or timing the call.

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