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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the agent knows this mutates state and is not repeatable. The description usefully adds the side effect that matched invoices become paid, but omits whether the match is reversible, how partial amounts are handled, and what authorization is required.

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?

A single tight sentence front-loads the action and resource with no filler. It is perhaps overly terse for a destructive operation, but every word earns its place.

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?

For a destructive, non-idempotent mutation with no output schema and zero schema coverage, the description conveys the core action and the key outcome (invoices become paid). It still leaves gaps around reversibility, partial matching, and error conditions that an agent would want before invoking.

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%, so the two required parameters rely entirely on the description. The prose maps naturally to both (a bank transaction and one or more approved invoices) and adds the constraint that invoices must be approved, but it gives no format or cardinality detail beyond 'one or more'.

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 states a specific verb (reconcile/match) and resources (bank transaction, invoices) and clarifies the outcome ('they become paid'). It distinguishes itself reasonably from read-side siblings like get_bank_transaction and from invoice-specific actions like approve_invoice, though it never names an alternative directly.

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 explicit guidance on when to choose this over siblings such as link_po, resolve_exception, or flag_bank_transaction, nor any stated preconditions beyond 'approved invoices'. The reconciliation context is implied but no exclusion or alternative routing is provided.

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