create_draft

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

With no annotations provided, the description carries the burden of behavioral disclosure. It only states that it creates a draft and requires an account, but does not mention that no email is sent, side effects, permissions, or what response to expect. This is minimal disclosure for a write operation.

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, concise sentence that front-loads the core action ('Create a draft email') and adds the key constraint ('one account'). There is no filler or repetition beyond the schema, making it highly efficient.

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?

Despite being a moderately complex tool with 11 parameters and no output schema, the description is only one short sentence. It does not explain the draft's behavior (not sent, stored as a draft), threading support, or how it relates to send/list/draft tools. Given the richness of the schema and sibling tools, this is insufficient contextual guidance.

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 description coverage is 100%, so the schema fully documents all 11 parameters. The description only adds the nuance of 'one account' and that account is required, which is already indicated by the schema's required list. This is a baseline score with no additional value.

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 clearly states the verb 'Create' and the resource 'draft email', and narrows scope to 'one account'. This distinguishes it from send/send_draft/list_drafts, though it does not explicitly name sibling alternatives. 'Draft' makes the intent unambiguous.

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 the tool is for creating drafts, not sending them, and the required account parameter is stated. However, it gives no explicit guidance on when to use this versus send_email/send_draft, and does not mention alternatives or exclusions.

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