unschedule_campaign

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

No annotations provided, so description carries full burden. It discloses that the tool changes status to draft, respects read-only and dry-run modes, requires API key authentication, and is subject to Mailchimp rate limits. Provides example return format.

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?

Front-loaded with core purpose, then structured details. Every sentence adds value, but could be slightly more concise. Example helps. Overall strong.

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?

Covers all needed aspects: purpose, status constraints, error handling, authentication, rate limits, dry-run, example, and relation to other tools. Output schema exists but description still explains returns adequately.

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 0% description coverage, but description adds detailed semantics: the campaign ID must be in 'schedule' status, includes an example format, and advises to obtain from list_campaigns(). This compensates fully.

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 verb 'Cancel' and resource 'scheduled campaign', and specifies the effect 'returning to draft status'. Distinguishes from siblings by explaining it only works on campaigns in 'schedule' status and mentions editing via update_campaign.

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 tells when to use: 'Use to cancel a scheduled send before it goes out'. Notes constraints: only works on 'schedule' status, returns error for drafts or sent. Provides alternative actions (edit via update_campaign) and mentions authentication and rate limits.

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