invoices-delete

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

The description only states that it deletes, which is obvious. It does not disclose potential side effects, such as cascading deletions, permission requirements, or whether the action is reversible. With no annotations, the description falls short of informing an AI agent about important behavioral traits.

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, which is concise and front-loaded. However, it is so minimal that it borders on under-specification.

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 delete operation, the description should mention prerequisites, irreversibility, and effects on linked data. It lacks these details. Despite low parameter complexity, the description is insufficient for safe and informed tool usage.

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 covers the single parameter with a description. The tool description adds no additional meaning beyond what the schema already provides. Given 100% schema coverage, a 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 states the verb 'Deletes' and resource 'an invoice', making the action clear. It distinguishes from siblings like invoices-create, invoices-get, invoices-update, which are the only related tools. However, it is somewhat redundant with the tool 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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., unlinking items before deletion) or when deletion is appropriate.

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