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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether the hold is reversible, what state the invoice enters, whether the note is stored, or what happens on repeat calls.

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 front-loaded sentence with no waste, but its brevity reflects under-specification rather than disciplined editing — it omits information the agent needs for a destructive mutation.

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-read-only state-changing tool with 0% schema description coverage and no output schema, the description is too thin: no effect description, no permission or prerequisite info, no guidance on the note field, and a misleading 'reason code' framing.

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 coverage is 0%, so the description must carry parameter meaning, and it does not. It mentions 'reason code' (suggesting a fixed enumeration) while the schema defines reason as an unconstrained string with no enum, which is actively misleading; invoice_id and note are never addressed.

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?

States a specific verb ('put on hold') and resource ('invoice'), which is distinct from approve_invoice and reject_invoice by name. However, it offers no explicit differentiation from siblings like dispute_invoice or escalate_exception, which are plausible alternative state transitions.

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 statement of when to hold versus dispute, reject, or escalate an invoice, and no prerequisites or conditions. The agent must infer usage entirely from the tool name and sibling list.

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