create-draft

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

No annotations are provided, so the description carries the full burden of behavioral disclosure and does very little with it. It does not say where the draft is stored, whether it is visible to recipients, whether 'from' defaults to the authenticated account, whether the draft can later be sent, or what is returned on success; for a write tool with zero annotation coverage this is a significant gap.

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?

A single front-loaded sentence with no filler, which is efficient. It is under-specified rather than bloated, so brevity here is a mild positive rather than a structural flaw.

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?

With no annotations, no output schema, and 0% parameter documentation, the description is the only guidance available and it covers roughly nothing beyond the tool's existence. An agent cannot determine required inputs, the role of the optional 'from' field, or the outcome of a successful call.

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 0% for all four parameters, so the description must compensate and does not. It never mentions 'to', 'subject', 'body', or the optional 'from', leaving the agent to infer the required fields and the meaning of the optional sender override from the property names only.

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?

States a specific verb (creates) and resource (draft email message), so an agent knows exactly what the tool produces. It does not differentiate from siblings, but none of the siblings (flag/list/move/read/search) overlap with draft creation, so the distinction is implicit rather than stated.

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?

No guidance on when to use this versus other tools, no prerequisites, and no mention of how a created draft relates to later sending or to read/list-email tools. The agent must infer the entire usage context from the name alone.

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