create_draft

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

With no annotations provided, the description carries the full behavioral disclosure burden. It does disclose a key behavioral trait: drafts are not sent through mail transport until explicitly sent. However, it does not mention persistence, idempotency, required mailbox existence, or any side effects beyond creating the draft.

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 with no filler. The primary action is front-loaded, and the clarifying sentence about mail transport is concise and valuable.

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?

For a tool with six parameters, no output schema, and no annotations, the description is too thin. It explains the draft concept but omits guidance on how to populate the optional fields, what the draft creation returns, or any constraints such as mailbox existence and recipient formatting.

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 only 33%, with domain and localPart explained but the other four parameters (to, html, text, subject) left undocumented. The description adds no parameter-level meaning beyond the schema, so it fails to compensate for the low coverage.

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 states a specific verb and resource: 'Create a draft on a mailbox.' It also distinguishes this tool from sending mail by explaining that a draft 'never goes through mail transport until sent,' which separates it from sibling tools like send_email and update_draft.

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 gives useful conceptual context, especially the contrast between a draft and a real message, but it does not explicitly name alternatives or state when to prefer create_draft over send_email or update_draft. The usage guidance is implied rather than explicit.

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