Delete Purchase Invoice

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that: it does not say whether deletion is permanent, whether confirmation is required, or what happens to linked documents, so it fails to earn credit beyond the annotations.

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?

The description is a single four-word phrase with no waste, but this is under-specification rather than conciseness. There is no structure to front-load and nothing that earns its place beyond echoing the title.

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 an irreversible destructive operation on an accounting document, the description omits confirmation semantics, preconditions, and downstream effects. No output schema exists and the annotations only flag destructiveness, so the description should carry more of this burden than it does.

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?

There is a single required parameter (id) and schema description coverage is 100%, so the schema fully documents it. With no parameter information in the description, the baseline of 3 applies.

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 repeats the tool title verbatim ('Delete a purchase invoice') and says nothing the name does not already convey. It does not distinguish this tool from the many other delete_* siblings (delete_sale_invoice, delete_journal, delete_transaction), so an agent gains no discriminating information.

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 prerequisites (e.g., must the invoice be unconfirmed or uninvalidated first?), and no mention of alternatives such as invalidate_purchase_invoice. The agent must infer all of this from the sibling list.

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