unschedule_campaign

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

Discloses that the operation transitions the status from 'schedule' to draft, only works on scheduled campaigns, returns an error otherwise, and provides the return format along with an error scenario. This adds significant value beyond the annotations which merely indicate non-readonly and non-idempotent.

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 concise at about 150 words, well-structured with clear sections (use case, args, returns, example), and front-loads the core purpose. Every sentence adds necessary information without redundancy.

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 simplicity (2 params, no nested objects, has output schema), the description covers all essential aspects: purpose, preconditions, postconditions, error handling, parameter details, and return format. The example validates the expected behavior. No gaps detected.

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 description explains the 'campaign_id' parameter with type, example, and validity constraints, compensating for the schema's 0% coverage. However, it omits any mention of the optional 'account' parameter, leaving a gap. For low coverage, this is partially helpful but incomplete.

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'), resource ('scheduled campaign send'), and outcome ('returning it to draft status for editing'). It distinguishes this tool from siblings like schedule_campaign, send_campaign, and pause_rss_campaign by specifying the exact action.

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 states when to use ('Use to cancel a scheduled send before it goes out'), when not to use ('returns error for drafts or sent campaigns'), prerequisite ('Only works on campaigns in 'schedule' status'), and provides a method to obtain valid campaign IDs ('Obtain from list_campaigns(status='schedule')'). Also mentions post-unscheduling steps.

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