Create Draft

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

No annotations provide behavioral hints (readOnlyHint, destructiveHint). The description states it creates a draft (non-destructive) and does not send, but lacks details on side effects, authentication, or other behaviors. It is adequate but minimal.

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 sentence efficiently conveys the purpose. No superfluous words. However, it could be slightly expanded to include key parameter context.

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 tool's low complexity and the presence of an output schema, the description covers the basic action. However, the complete lack of parameter documentation is a notable gap for completeness.

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 has 4 parameters, all with 0% documentation coverage. The description does not mention any parameter meanings, formats, or constraints, leaving the agent to rely solely on parameter names and types.

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 'Mail draft', and distinguishes this tool from the sibling 'mail_send' by adding 'without sending'. It is specific and differentiates effectively.

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 phrase 'without sending' provides clear context that this tool is for creating drafts not to be sent immediately. However, it does not explicitly define when not to use it or directly name alternatives like 'mail_send'.

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