delete_draft

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

Description states 'Permanently delete' and 'Irreversible', but annotations have destructiveHint: false, indicating the operation is not destructive. This is a direct contradiction, so score is 1.

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?

Two sentences, front-loaded with core action, no unnecessary words. Every sentence adds value.

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 deletion tool with one parameter, the description covers scope, irreversibility, and IMAP distinction. Missing return value details but acceptable given common expectations for delete operations.

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?

Schema coverage is 100% and the schema description already explains the parameter. The description adds no new meaning beyond what the schema provides, so 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?

Clearly states 'Permanently delete a locally saved draft from SQLite', specifying verb (delete) and resource (locally saved draft). Distinguishes from sibling tools by noting it does not affect the Proton Drafts IMAP folder.

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?

Explicitly says 'Use to discard a draft you no longer need' and provides a clear exclusion: 'Does NOT remove a matching draft from the Proton Drafts IMAP folder — that requires a separate mailbox action.' Guides when to use and when not to.

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