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

With no annotations, the description carries the full burden and largely meets it by disclosing what the tool actually does: extracts transactions, computes totals, and detects specific discrepancy classes (missing commission, wrong rate, duplicates, math errors) plus risk flags. It stops short of describing permission needs, cost, or how results are surfaced, but the behavioral profile is far richer than the name alone.

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 sentences, front-loaded with the core verb+resource before the capability list and audience. No filler, though the trailing audience list is somewhat expendable and the discrepancy enumeration could be tightened.

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?

There is no output schema, and the description does a reasonable job of telling the agent what comes back (transactions, totals, discrepancy detections, risk flags) so the agent can anticipate return content. Remaining gaps are minor: no detail on output structure or behavior when expected_total is omitted.

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 three parameters (statement_text, expected_total, currency) are already documented in the schema. The description alludes to the expected-total comparison but adds no new syntax, format, or constraint detail beyond what the schema provides, so the baseline of 3 applies.

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 names a specific verb (parse, reconcile) and resource (commission statement) and then enumerates the concrete operations performed: extracting transactions, computing totals, detecting discrepancies, and flagging risks. There are no siblings to differentiate from, but the purpose is unambiguous and far beyond a restatement of the title.

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 gives an audience (brokers, sales ops, affiliate managers) and mentions reconciling against an expected total, which implies the use case. However, it never states when to use this versus any alternative, nor any prerequisites or exclusions for the statement input.

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