Schedule Email

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

Annotations only provide readOnlyHint=false, destructiveHint=false, and idempotentHint=false, which convey minimal behavior. The description adds valuable behavioral traits: retry behavior (up to 3 times) and specific time windows. It does not cover failure/success details but is adequate given the annotations.

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 sentences, no filler, front-loaded with purpose, and efficiently includes constraints, retry info, and cross-references to sibling tools. Every sentence earns its place.

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 covers the essential constraints (time windows, retries) and points to related tools for further actions. With an output schema present, the missing return value explanation is not a gap. The tool's complexity is moderate, and the description is complete for an agent to use it correctly.

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 80%, so the description does not need to add much for parameters. The description adds no extra parameter meaning beyond the schema (e.g., ISO 8601 format for send_at is already in schema). Hence baseline 3 is appropriate.

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 action ('Schedule an email for future delivery') and provides specific constraints (minimum 60 seconds, maximum 30 days), which distinguishes it from siblings like 'send_email' for immediate sending, and mentions related tools 'list_scheduled_emails' and 'cancel_scheduled_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?

The description gives clear context on when to use this tool (future delivery) and directs to sibling tools for viewing or canceling scheduled emails. However, it does not explicitly state when not to use it (e.g., for immediate sending use 'send_email'), though this is implied by the constraints and sibling names.

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