delete_invoice

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states the basic action without revealing consequences (e.g., irreversibility, impact on related records, or authorization needs). 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 a single short sentence, easy to parse and front-loaded with the action. Minor redundancy exists in 'cancel or delete', but overall it is concise and free of filler.

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 one-parameter tool with no output schema, the description is functionally adequate. However, it omits important behavioral context (such as whether deletion requires special permissions or whether it is reversible), which a caller would benefit from knowing.

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 already describes the invoice_id parameter clearly, and schema coverage is 100%. The description adds minimal extra meaning beyond confirming that deletion is by UUID, so it meets the baseline for schema-covered parameters without enriching semantics further.

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 the action (cancel or delete) and the resource (invoice) with a specific identifier (UUID). It is distinct enough from sibling tools like create_invoice or list_invoices, though the dual verb 'cancel or delete' introduces slight ambiguity about the exact operation.

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, nor any prerequisites such as invoice status or permission requirements. No exclusions or contextual conditions are mentioned.

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