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. It says 'Delete' but does not state that the operation is irreversible, whether it cascades to related records, what permissions are required, or what happens to issued/e-factura invoices.

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 sentence is short and front-loaded with the action and resource, with no wasted words. It is perhaps overly terse for a destructive operation, but from a pure conciseness standpoint it is efficient.

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 tool with no annotations and no output schema, this description is not complete enough. It should disclose irreversibility, side effects, and any restrictions on deleting invoices, especially given the many similar supplier/proforma invoice deletion siblings.

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 already explains that the id is an invoice ID from search_invoices. The description merely repeats 'by ID' without adding format details, examples, or constraints, so the baseline 3 is appropriate.

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 resource (invoice) plus the lookup key (ID), so an agent can tell what the tool does. It does not distinguish itself from the many sibling delete tools such as delete_supplier_invoice, delete_proforma_invoice, or delete_simplified_supplier_invoice, which is a meaningful gap in this family.

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 tool versus update_invoice, get_invoice, or the closely related delete_* siblings. It also omits any prerequisite conditions, such as whether the invoice must be in a particular state before deletion or what to do if it has already been issued or sent.

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