send_draft

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

With no annotations, the description carries the full burden of disclosing side effects. It explicitly states 'The draft is moved from Drafts to Sent Items,' which is a clear behavioral consequence beyond a simple 'send' action. It does not mention permissions or error conditions, but for a simple mutation, the disclosed folder transition is valuable.

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 concise sentences, front-loaded with the primary action and immediately followed by the key behavioral outcome. Every word earns its place with no unnecessary detail.

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 simple one-parameter tool with no output schema and well-documented parameter in the schema, the description adequately covers purpose and side effect. It could mention the expected return value or success/failure behavior, but the tool is simple enough that the current description is largely complete.

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 input schema already provides 100% coverage for the single parameter messageId, including a descriptive explanation listing the exact draft-creating functions. The description adds no additional parameter semantics, so the baseline of 3 applies.

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 uses a specific verb and resource: 'Send a draft message,' and further clarifies the action by stating the draft is moved from Drafts to Sent Items. This clearly distinguishes it from sibling tools like send_email, which sends a composed message not necessarily a 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 clearly indicates this tool is for sending draft messages, providing context that it should be used when a draft needs to be sent. It does not explicitly mention alternatives or exclusions, but the draft-specific language and folder behavior effectively communicate when to use it.

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