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

Annotations already signal idempotent and non-destructive behavior, so the description is not required to restate those. It adds valuable behavioral context by revealing that omitting transactionId clears an existing match and that closed statements reject the call.

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 contain the core action, the alternative clearing mode, and the closed-statement constraint. No filler or redundant restatement of the title/schema.

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?

With an output schema and annotations covering idempotence/destructiveness, the description covers the essential behavior and constraints. It leaves minor gaps such as defining 'closed statement' or how to obtain lineId, but nothing critical for a competent agent invocation.

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?

Although every parameter has a schema description, they are all only 'UUID value wrapper,' so the free-text description must carry real meaning. It does: 'ledger transaction settles a bank-statement line' maps transactionId and lineId to their roles, and 'omitting the transaction' explains the optional parameter's clearing behavior.

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?

Description uses a specific verb 'Record' and names the exact resource: a ledger transaction settling a bank-statement line. It also distinguishes this confirmation tool from suggestion siblings by covering both confirm and clear behaviors.

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 what the tool does and provides a concrete usage mode ('clear an existing match by omitting the transaction'), plus a refusal condition ('Refused once the statement is closed'). However, it never names any alternative sibling such as accounting_suggest_statement_matches, so an agent must infer when to choose this over related tools.

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