Create Draft Email

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

No annotations are provided, so the description must carry the full burden. It does not disclose behavioral traits such as authentication requirements, limitations on drafts, or side effects beyond creating the draft. It lacks details on what happens if the account is invalid or if parameters are malformed.

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 two sentences long, front-loads the core purpose, and contains no extraneous information. Every word earns its place.

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?

Given the complexity (8 parameters, no output schema), the description is insufficient. It does not explain the return value (e.g., draft ID), error handling, or interaction with sibling tools. The tool requires more 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?

The schema description coverage is 50% (4 of 8 parameters described). The description adds general context but does not detail each parameter beyond what the schema provides. It does not compensate for the undocumented parameters (cc, bcc, subject, body).

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 'a draft' and specifies the platform 'Gmail or Microsoft 365'. It also distinguishes itself as a write path before sending, differentiating from sibling tools like send_draft or send_mail.

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 says 'preferred write path before sending', implying it should be used to prepare an email before sending. However, it does not explicitly state when not to use it or mention specific alternatives like send_draft or send_mail.

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