cancel_single_send_schedule

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

With no annotations, the description carries the full burden. It discloses that the tool is mutating and preserves the draft, which is helpful. However, it omits potential side effects, permission requirements, or confirmation of success/failure beyond the basic 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?

A single sentence front-loaded with 'Mutating' immediately signals the tool type. Every word adds value: no redundancies or fluff.

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 low complexity (1 parameter, no output schema), the description covers the key action and side effect (draft preservation). However, it lacks details on return values, error conditions, or confirmations. The context is adequate but not thorough.

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?

The input schema already describes the parameter 'single_send_id'. The description adds context by specifying it applies to a 'scheduled' Single Send, which clarifies the scope beyond the schema's generic 'Single Send ID'.

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 verb 'cancel' and the resource 'scheduled Single Send', and distinguishes itself from 'delete_single_send' by clarifying that the draft is not deleted. This provides specific, actionable purpose.

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 implies usage via the distinction from deletion, but does not explicitly state when to use this tool versus alternatives like 'delete_single_send' or 'schedule_single_send'. No when-not-to-use guidance is provided.

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