Cancel Scheduled Email

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

Annotations declare idempotentHint=true and destructiveHint=false. Description adds that cancel returns false if ID not found or email sent, clarifying safety and idempotency. Provides enough behavioral context beyond 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: first defines action and target, second explains return behavior. No unnecessary words. Perfectly 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?

For a cancellation tool with clear annotations and a well-documented schema, the description is complete. It explains what happens under different conditions (ID found/sent or not) and implies the prerequisite steps (having scheduled an email). No gaps.

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?

Input schema has 100% description coverage with clear explanations for both parameters. The tool description does not add further information, but the schema already does the job. Baseline score 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?

Clearly states the tool cancels a pending scheduled email. The verb 'cancel' and resource 'pending scheduled email' are specific and distinct from sibling tools like schedule_email and list_scheduled_emails.

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?

Implies usage when an email has been scheduled but not yet sent. Mentions return false conditions for missing or already-sent emails. The id parameter description further guides obtaining IDs from schedule_email or list_scheduled_emails. Lacks explicit 'do not use if already sent' but is clear enough.

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