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

Annotations already establish readOnly/non-destructive/openWorld=false, so the bar is lower, and the description still adds real behavior: missing costs remain unknown rather than being coerced to zero, and a declaredTotal can be checked against the computed sum. The auth/cost disclosure ('No key, credits or wallet') is useful, though 'FREE during validation' is ambiguous about what changes afterward.

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 core purpose is front-loaded in the first clause and the whole thing is only three short sentences. The cost/auth sentence is telegraphic and slightly noisy for a read-only reconciliation tool, but nothing is redundant.

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. Given a read-only annotation set, the description covers the operation, the null-handling rule, the optional total check, and access requirements, leaving no gap an agent must fill before calling it.

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 67%, so the schema does most of the work on the nested input object. The description adds 'exact decimals' (hinting at the string-decimal pattern) and names the component fields and declaredTotal, but it explains nothing about currency/minorUnitDigits semantics or how the optional legacy fields (requestId, maxPriceMicroUsd) are handled beyond the schema note.

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?

States a specific verb (reconcile) and enumerates the resource components it operates on (item, discount, shipping, tax, fee amounts), plus the mechanism (exact decimals). This is far more informative than a tautology, but it never distinguishes itself from adjacent siblings such as commerce_unit_price or commerce_money_parse, which an agent could plausibly confuse it with.

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 statement of when to pick this tool over the many commerce_* siblings, nor any precondition or exclusion. The only usage-flavored sentence, 'Existing source and input limits apply,' is too vague to route an agent, and 'FREE during validation' is a pricing note rather than guidance.

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