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

No annotations are provided, so the description carries the full burden of behavioral disclosure for a destructive operation — yet it says nothing about irreversibility, required permissions, whether linked records are affected, or behavior when the ID does not exist. The verb 'delete' only implies mutation; no additional behavioral context was added.

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 no filler, and the resource and identifier come first. Nothing is wasted; the gap is under-specification rather than verbosity.

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 one-parameter destructive tool with no annotations and no output schema, the description should at minimum cover irreversibility, error behavior on unknown IDs, and its distinction from delete_supplier_proforma_invoice. None of that is present.

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 only one parameter and the schema documents it fully (100% coverage) as 'Proforma invoice ID'. The description's 'by ID' adds no meaning beyond the schema, which is the expected baseline for a single well-documented parameter.

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 and resource ('Delete a proforma invoice') plus the identifier used, so the agent knows exactly what the tool does. It does not differentiate itself from the sibling delete_supplier_proforma_invoice, which is a real ambiguity risk given the near-identical name.

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?

No guidance on when to use this versus delete_supplier_proforma_invoice, no prerequisites, and no note that the ID likely comes from search_proforma_invoices. The agent must infer everything about selection.

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