cancel_campaign

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

Given no annotations, the description discloses key behavioral traits: the campaign must be currently sending and the operation only works during the send window. It does not describe post-cancellation effects, but an output schema exists (not shown) which may cover return values.

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?

Two sentences with no redundant information. The first sentence states the action and resource, the second adds the critical constraint. Efficient 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?

For a simple tool with one parameter and a condition, the description is mostly complete. It covers the main precondition and limitation. Not mentioning error handling or fallbacks is acceptable given the tool's simplicity and the existence of an output schema.

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 description coverage is 0%, so the description should add meaning to the sole parameter campaign_id. It does not explain the parameter beyond its name or provide any format/constraints, leaving the agent to infer from context.

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 action (cancel) and the specific resource (campaign that is currently sending). It distinguishes from siblings like delete_campaign by specifying the condition 'currently sending'.

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 provides a limited usage guideline: 'Only works during the send window.' However, it does not explicitly state when not to use it or mention alternatives like delete_campaign or unschedule_campaign for campaigns not in the send window.

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