cancel-scheduled-send

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

No annotations provided, so description carries full burden. It discloses the safety implication (prevents future action), return value (cancelled schedule, leaves draft), and need for confirmation. Does not cover all potential errors but adequate for main behavior.

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?

Very concise with 4 sentences, each serving a distinct purpose (use case, return, exclusions, safety). Well-structured and front-loaded.

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 the tool's simple nature and existence of output schema (not shown but signaled), the description covers all needed aspects: when to use, when not, safety, return, and parameter semantics.

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 0% but description explains that 'confirmed' requires explicit confirmation before setting to true, and 'schedule_id' must be the exact one from user. Adds meaning beyond schema pattern and required fields.

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 tool's action: 'preventing one pending Apple Mail scheduled send'. It uses a specific verb (cancel) and resource (scheduled send), and distinguishes from sibling tools like reschedule-scheduled-send.

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?

Explicitly provides 'Use when:' and 'Do not use when:' conditions, including when the job is already sending or terminal. Also includes safety warning requiring explicit confirmation.

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