create_draft

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

Discloses that email is not sent and optional threading. No annotations present, so description carries full burden; lacks details on storage, permissions, or lifecycle of the draft.

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 concise sentences with no extraneous information. Front-loaded with key action and state (not sent).

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 creation and threading but lacks explanation of how other parameters like cc, bcc, isHtml are used. No output schema leads to missing return value details.

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%, so baseline applies. Description adds minimal meaning beyond schema, only hinting at threadId usage for draft reply. No format or behavior specifics for parameters.

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 it creates a draft email that is not sent, and optionally attaches to a thread. This distinguishes it from send_email and reply_email among siblings.

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?

Implies use when a draft is needed, not sent. Mentions thread attachment option but lacks explicit comparison to reply_email or send_email for deciding between draft or direct send.

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