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

Annotations already flag destructiveHint=true and non-idempotent, so the safety profile is covered; the description goes beyond that by explaining what each action actually does — accepting puts the invoice on the bill, removing discards the held copy so a corrected one can replace it. It adds the operational caution 'Ask the trade first,' which is genuine guidance not present in any structured field, though it says nothing about reversibility or failure behavior.

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, with the scoping precondition front-loaded and the two branches laid out in parallel. Every clause adds information; 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?

For a two-parameter destructive tool with no output schema, the description supplies the precondition, both action semantics, their consequences, and a caution to confirm with the trade. The remaining gap — what a successful response looks like and whether removal can be undone — is minor but real for a destructive operation.

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 description carries the burden and does so for the enum: both 'accept' and 'remove' are given concrete meaning and downstream consequences. The invoice_id parameter is left unexplained, but its meaning is self-evident from the tool's stated precondition.

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 the resource (an invoice held back as needs_check) and the two specific operations (accept as read, remove), so an agent knows exactly what the tool does. It does not reference any sibling tool, but none of the listed siblings appear to overlap, so differentiation is achieved by the precondition rather than by explicit contrast.

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 states a clear precondition — the invoice must be in the needs_check state — and explains the outcome of each branch, which effectively tells the agent when this tool applies. It stops short of stating what to do for invoices not in that state, leaving that boundary implicit.

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