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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=false, and readOnlyHint=false, so the safety profile is partly covered. The description adds nothing on top: it never says what disputing does (vendor notified? invoice locked? state transition?), whether it is reversible, or what permissions are needed for an irreversible destructive action.

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?

It is a single short sentence with no filler, but that brevity here is under-specification rather than economy. The one clause that exists is front-loaded correctly.

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, state-changing invoice operation with zero parameter documentation and no output schema, the description is materially incomplete. An agent cannot tell what side effects to expect, which makes invoking an irreversible action risky.

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 full burden and fails it. Neither the required 'reason' nor the optional 'note' is explained (allowed values, length, how the reason is conveyed to the vendor), and 'invoice_id' is only implied by the phrase 'an invoice'.

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 has a specific verb and resource ('Dispute an invoice'), and 'with the vendor' hints at the external party involved. It does not, however, distinguish this action from the sibling lifecycle tools (approve_invoice, reject_invoice, hold_invoice), so an agent must infer the difference from the name alone.

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 when-to-use guidance, no preconditions, and no mention of alternatives such as approve_invoice, reject_invoice, or hold_invoice that also act on invoices. The agent gets no rule for choosing dispute over rejection or escalation.

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