send_email

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

Discusses the draft/send behavior and auto-linking to contacts, but does not cover error scenarios, rate limits, or what happens when the account is not connected. Given no annotations, it is adequate but not exhaustive.

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?

Three sentences with clear structure. First sentence provides a high-level summary, followed by details. No fluff, but could be slightly more concise.

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?

Given 8 parameters and no output schema, the description covers the main workflow and key behavioral details, but omits return value and error handling. It is moderately 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?

Schema coverage is 100% (baseline 3). The description adds value by explaining the draft parameter's default and usage, and the format of the 'to' parameter. Other parameters are sufficiently described in the schema.

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 composes an email and either sends or saves as draft. Distinguishes the main action (compose and send/save) but does not differentiate from sibling tools like update_email.

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?

Provides clear guidance on when to use draft=true (default) vs false (only when user explicitly asks to send). Mentions prerequisite of a connected email account and references list_email_accounts. Also explains provider-specific behavior for Outlook vs others.

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