send_draft

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

The description states the draft is moved to Trash after sending, which is a destructive action, but the annotation `destructiveHint` is false. This is a direct contradiction, indicating serious inconsistency.

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?

Extremely concise: a single sentence that conveys the core action and outcome with no unnecessary 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?

The description is incomplete given the contradiction and lack of detail about side effects or the output schema. For a simple tool with one parameter, it should provide more clarity about behavior.

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 coverage is 100%, and the parameter `uid` is described in the schema as 'Draft IMAP UID'. The description adds no additional semantic meaning beyond this.

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 'Send' and resource 'draft by UID', and adds the post-action 'move to Trash', making it distinct from siblings like `save_draft` or `list_drafts`.

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 explicit guidance on when to use this tool versus alternatives such as `send_email` or `save_draft`. The description does not mention prerequisites or contexts where this tool is inappropriate.

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