delete_invoice

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

With no annotations, the description carries the full burden, and it does disclose one meaningful trait: the transaction record is retained rather than removed. It omits other essentials for a mutation, such as required permissions, whether the void is reversible, which invoice states can be voided, and whether the voided invoice still appears in reports.

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 eleven-word sentence with the action front-loaded and a key consequence appended. There is no filler, and the retained-record behavior is stated right where the agent needs it.

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-adjacent mutation with no annotations, no output schema, and an undocumented nested parameter, the description is too thin. It covers intent but not preconditions, response shape, or failure modes, so an agent could invoke it on an invalid invoice state without warning.

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% and the single parameter is an opaque, untyped "idOrEntity" nested object with additionalProperties allowed, so the schema explains nothing. The description adds no clarification of whether an ID, an entity object, or both are accepted, leaving a genuinely ambiguous input unresolved.

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 a specific verb and resource ("Void an invoice") plus the platform (QuickBooks Online), which is enough to separate it from read_invoice, update_invoice and create_invoice. The phrase "preserving its transaction record" also distinguishes voiding from a hard delete like delete_bill/delete_item. It stops short of a 5 because it never explicitly routes against a sibling.

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 when-to-use or when-not-to-use guidance: nothing says when to void rather than issue a credit memo or refund receipt, and no prerequisite invoice state is given. "Preserving its transaction record" hints at the void-vs-delete tradeoff but leaves the agent to infer it.

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