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

With no annotations, the description carries the full burden of behavioral disclosure, and it only says 'delete'. It does not state whether deletion is permanent or reversible, what happens to linked records, whether it requires special permissions, or what is returned on success or failure — all critical for an irreversible mutation.

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 short sentence with the action and scoping front-loaded and no wasted words. It is efficient, though being this terse contributes to the behavioral gaps noted elsewhere.

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, irreversible operation with zero annotations and no output schema, the description should explain consequences, confirmations, or failure modes. None of that is present, so an agent cannot predict the effect of calling it beyond 'something gets deleted'.

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 100% and the schema itself explains that the ID comes from search_supplier_proforma_invoices. The description's 'by ID' adds no meaning beyond that, so the high-coverage 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 states a specific verb (delete) and a precise resource (supplier proforma invoice) scoped by ID, which cleanly separates it from delete_proforma_invoice and delete_supplier_invoice by name alone. It stops short of any explicit differentiation sentence, but the resource name is unambiguous.

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 guidance on when to use this versus the sibling delete tools, nor any prerequisite such as looking the invoice up via search_supplier_proforma_invoices first. The only hint toward usage is incidental, appearing in the schema's parameter description rather than the tool description.

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