cancel_scheduled_email

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

With no annotations, the description carries the burden. It explicitly states the tool is a [mutation] and that it deletes the email, and requires confirmation. This discloses the core behavioral traits, though it could add details like irreversibility or side effects.

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?

The description is very concise: two sentences total, front-loaded with the purpose and followed by a crucial usage note. No 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 10 parameters with full schema coverage and no output schema, the description is minimal but covers the essential action, mutation flag, and confirmation requirement. It could explain return behavior or that the email is permanently deleted, but it's minimally adequate.

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%, so the description adds marginal value. It reinforces the confirm parameter's role as a confirmation flag. 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 it cancels a scheduled email and deletes it. The verb 'Cancel' and resource 'email programado' are specific. Among siblings like cancel_scheduled_message and cancel_campaign, this tool is distinctly for email cancellation.

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 mentions the action is a mutation requiring confirmation (confirm=true), which provides clear usage context. However, it does not explicitly differentiate from other cancellation tools or state when not to use this tool.

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