Send Email

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly states the confirmation requirement, the one-email-per-call limit, and the fact that only the user's own saved Gmail draft is sent. This is valuable safety-relevant behavior beyond a generic 'send email.'

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 compact and front-loaded with the core purpose. Each sentence delivers distinct guidance: what it sends, the confirmation requirement, and a clear anti-loop instruction. 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?

The tool is simple, all parameters are fully documented in the schema, and an output schema is present. The description supplies the behavioral guardrails an agent needs—confirmation, single-send, and no looping—so nothing critical is missing.

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 100%, so the schema already documents all parameters. The description reinforces confirm=True as an explicit human approval, which adds a nuance, but it does not substantially expand on draft_id or to_email beyond what the schema provides.

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: 'Send exactly one saved draft from the user's own Gmail account.' It clearly differentiates from sibling tools like save_outreach_draft or suggest_email by emphasizing it sends an existing draft, not creating or suggesting one.

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 strong usage constraints: confirm=True must be an explicit human yes, one call sends one email, and never loop over contacts. It does not explicitly compare to alternatives, but the when-to-use guidance is clear and actionable.

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