delete_draft

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

Explicitly states the deletion is permanent and irreversible, and specifies it operates on local SQLite storage only. No annotations, so description provides crucial behavioral details. Could add error handling details, but sufficient for a simple deletion.

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?

Three concise sentences, each carrying essential information: purpose, usage guidance, and a critical behavioral note. No redundant or filler content.

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?

Covers operation, usage context, limitations, and irreversibility. Lacks error handling or return value details, but since no output schema, it's acceptable for a simple deletion tool.

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 covers draftId description 100%, stating it comes from local draft creation/list calls. Description repeats the local nature but does not add new semantic details beyond schema.

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 it permanently deletes a locally saved draft from SQLite, specifying the resource and action. Differentiates from remote deletion and other draft actions, and notes it is separate from mailbox operations.

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?

Provides clear guidance on when to use (discard a draft no longer needed) and explicitly states it does not remove from IMAP folder, implying alternative action needed. Lacks explicit naming of sibling tools but still informative.

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