Save draft

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

No annotations provided. Description notes the non-sending behavior, but omits other behavioral traits like attachment handling, draft storage location, or server-side persistence.

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, no fluff, directly informative. Ideal length for a tool with clear purpose.

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?

No output schema, no description of return value or error conditions. For a complex tool with 9 parameters, the description is insufficient for an agent to use it confidently without additional context.

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 low (44%) and description adds no additional information beyond the schema. For example, the 'subject' parameter is required but undocumented, and 'cc'/'bcc' lack descriptions. The description should compensate for this gap.

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 saves a draft and notably clarifies it does not send the email, distinguishing it from sibling tools like send_email and compose_preview.

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 'Does not send', implying use when the user wants to review later. However, it does not provide guidance on when to use alternatives like compose_preview, forward, or reply.

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