send_draft

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

No annotations provided. Description discloses immediate sending and user approval requirement but omits details on irreversibility, permissions, or error states.

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?

Two efficient sentences, front-loaded with key context (multi-account, send draft). 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?

No output schema, but description adequately covers purpose, account selection, and user approval. Could mention return value (e.g., message ID) or error handling.

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?

Account parameter has helpful description referencing list_accounts. DraftId parameter lacks description beyond type string; only 50% schema coverage, so description adds some value but not fully compensates.

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?

Clearly states it sends an existing draft and specifies the multi-account Gmail context. Distinguishes from siblings like create_draft and send_message.

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?

Indicates user approval is required, implying appropriate use after consent. Does not explicitly list when not to use or alternatives, but context is clear.

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