Supprimer une facture

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

The description adds an explicit warning about irreversibility beyond the annotations (destructiveHint=true). It matches the annotation and provides clear behavioral context, though it doesn't detail consequences on related data.

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 extremely concise with two short sentences, no redundant information, and the warning is front-loaded for immediate attention.

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?

Given the simplicity of the tool (delete by ID), the description is sufficient. Annotations cover destructive behavior, schema covers the parameter, and the irreversibility warning adds necessary context. No output schema is needed for a delete operation.

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?

The schema coverage is 100%, and the description adds no additional meaning to the id parameter beyond what the schema provides. The baseline score of 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 clearly states that the tool deletes an invoice (Supprime une facture). It uses a specific verb and resource, and distinguishes itself from sibling invoice tools like create, get, search, and update.

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?

The description mentions the action is irreversible, which is a key usage warning. While it doesn't explicitly state when to use versus alternatives, the delete operation is straightforward and the sibling tools provide clear context for other operations.

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