save_draft

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the action and folder, adding minimal context. It does not mention permissions, return values, behavior on missing/invalid fields, or whether it overwrites existing drafts—leaving significant gaps for a mutation tool.

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 sentence, immediately states the verb and object, and includes a clarifying parenthetical. Every word earns its place, with no filler or repetition.

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?

The tool is simple but has 4 parameters (2 required) and no output schema or annotations. The description does not explain the overall behavior beyond 'save as draft', nor does it cover preconditions, edge cases, or what success looks like. The schema helps with parameters but the description fails to provide adequate context for safe invocation.

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 has 100% coverage with descriptions for all parameters (to, subject, html, text). The tool description adds no parameter-specific information, so it does not go beyond what the schema already provides. Baseline 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 'Save email as draft (IMAP DRAFT folder)' uses a specific verb ('Save') and resource ('email'), and explicitly states the destination folder, making it clear this is for draft creation rather than sending. It distinguishes from sibling tools like send_email and move_email by emphasizing the draft nature.

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?

The description implies usage for saving drafts but does not explicitly contrast with alternatives like send_email (which sends immediately) or mention when not to use it. The parenthetical 'IMAP DRAFT folder' provides context but no explicit when/when-not guidance.

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