create_draft

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

Annotations already declare readOnlyHint=false and destructiveHint=false, giving a basic safety profile. The description adds the key behavioral fact that the message is not sent, which is beyond annotations. However, it does not disclose other behaviors such as persistence, return value, or whether drafts are immediately visible, so the addition is modest.

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 sentence with no wasted words, which is structurally concise. However, it is severely under-specified, failing to provide adequate information for correct tool usage. This is under-specification rather than commendable conciseness.

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 5 parameters, no output schema, and zero parameter documentation in the description, the tool is inadequately specified. The description does not explain expected inputs, output, or side effects beyond the basic 'create a draft' notion, leaving the agent to guess at 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 description coverage is 0%, so the description must compensate for parameter meaning. It provides no clarification for parameters like 'html' (whether body is HTML) or 'cc' (array of addresses), leaving the agent to rely solely on schema types without semantic context.

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 'Create a draft message (not sent)' has a specific verb and resource, and explicitly clarifies that the message is not sent. This distinguishes it from send_mail and send_draft, making the purpose 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?

No guidance is provided on when to use this tool versus alternatives like send_draft or update_draft. The parenthetical '(not sent)' implies use for preparing messages, but no explicit circumstances, prerequisites, or exclusions are given.

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