create_draft

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

Annotations indicate a non-read-only, non-idempotent write operation. The description adds that it saves the exact draft and that the broker cannot send, which clarifies that no transmission occurs. However, it doesn't detail whether each call creates a new draft or what the response contains, leaving some behavioral aspects undisclosed.

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?

Single sentence, 12 words, front-loaded with the core action. No wasted words.

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 create tool with output schema and annotations, the description is minimally sufficient but lacks guidance on usage context and parameter roles. Given the moderate complexity (7 parameters) and sibling update_draft, more detail would improve 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?

With 0% schema description coverage, the description needed to explain parameter meaning, but it only says 'exact draft,' giving no detail on account_id, to, subject, body, or optional fields. The tool name and schema titles provide basic hints, but the description adds little beyond that.

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 'Save this exact draft' clearly identifies the action (save) and object (draft). It adds the broker's lack of send capability, which clarifies the tool's scope and distinguishes it from a send operation, though it doesn't explicitly differentiate from 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 'no send capability' note provides context that this tool is for drafts rather than sending, but it doesn't explicitly state when to use create_draft versus the sibling update_draft. The name implies creating a new draft, but the description offers no direct guidance on alternative tools.

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