delete_invoice

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

No annotations are provided, and the description does not disclose behavioral traits beyond the basic action. It does not state whether the operation is irreversible, what permissions are required, or if there are any side effects like cascading deletions. For a destructive operation, this is a significant gap.

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 very concise at two sentences, including the HTTP method and path. It is front-loaded and contains no extraneous information. However, it could be slightly more structured, e.g., by separating the action from the endpoint reference.

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 simple delete operation with one parameter and no output schema, the description is minimally adequate. It states the action and the required parameter but lacks context about effects on related resources, error conditions, or comparison to similar tools like void_invoice. Given the complexity, additional context would be beneficial.

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 input schema has 100% coverage with the single required parameter 'invoiceId' described as 'Invoice ID (required)'. The description adds no additional meaning, such as expected format, where to obtain the ID, or any constraints. Baseline score 3 applies due to full schema coverage.

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 'Delete an invoice', which is a specific verb+resource. It distinguishes from sibling tools like create_invoice, update_invoice, and void_invoice by indicating the delete action. However, it lacks any further clarification about the scope or consequences of deletion.

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 provides no guidance on when to use this tool versus alternatives such as void_invoice or charge_invoice. It does not specify prerequisites, such as the invoice needing to exist or be in a deletable state, nor does it mention any conditions under which deletion is appropriate.

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