delete_invoice

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

The description only restates the tool's purpose and adds no behavioral context beyond annotations. While annotations declare destructiveHint=true and readOnlyHint=false, the description does not disclose whether deletion is permanent, cascading, or has any side effects.

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, front-loaded sentence with no redundant words. It is perfectly concise for the simple action it describes.

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 presence of destructiveHint and openWorldHint, the description is minimal but lacks critical context about the deletion's impact, such as whether it is reversible, if related items are affected, or any restrictions. The tool is too thin to be fully complete for a destructive 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 fully describes the sole parameter invoice_id, achieving 100% coverage. The description contributes no additional parameter meaning, so it meets the baseline for schema-rich tools without raising the score.

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 uses a specific verb ('Delete') and resource ('an invoice'), clearly distinguishing it from sibling tools like create_invoice, get_invoice, or update_invoice. It precisely states the action performed.

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 such as cancel_invoice or issue_invoice. It does not mention acceptable use cases, prerequisites, or scenarios where deletion is not recommended.

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