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

Description clearly indicates the destructive nature by using 'Discard' and 'remove'. Annotations support this with destructiveHint=true and readOnlyHint=false. No contradiction or hidden behavior.

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?

Description is concise, using two short sentences with no unnecessary words or repetition. It is well-structured and easy to parse.

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, the description and annotations provide all necessary context: what it does, when to use it, and how it differs from the send alternative. No critical information is missing.

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 only parameter id is fully covered by the schema description 'Draft ID.' The tool description does not add extra meaning beyond the schema, but with 100% schema coverage this is sufficient.

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?

Description clearly states the tool discards/removes a draft, with the specific resource being email drafts. It also distinguishes itself from email_draft_send, which is the sibling for delivering drafts.

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 tells when to use this tool: to remove drafts no longer needed. It also explicitly tells when not to use it and which alternative to use (email_draft_send for delivering).

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