delete_campaign

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

Annotations indicate destructiveHint=true and idempotentHint=true. The description adds that deletion is permanent, only works on non-sent campaigns, and returns an error for sent ones. It also details the return format (status, campaign_id), providing significant behavioral context beyond annotations.

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 efficiently structured with a clear main sentence, bulleted usage notes, and explicit Args/Returns/Example sections. Every sentence adds value, and it is appropriately sized for the tool's complexity.

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 has 2 parameters (1 required), annotations, and an output schema, the description covers purpose, constraints, parameter usage, return format, and an example. It is complete and leaves no critical gaps for an agent.

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 0%. Description explains campaign_id with example and constraint ('Must not be a sent campaign'), but does not document the optional account parameter (anyOf string/null). So only one of two parameters gets semantic information, partially compensating.

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 starts with 'Permanently delete a campaign from the account', clearly stating the verb (delete) and resource (campaign). It further specifies it only works on unsent campaigns, distinguishing it from other delete tools like delete_audience or delete_member.

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?

Provides explicit guidance: 'Use to remove unwanted draft or scheduled campaigns. Only works on campaigns that have not been sent... Sent campaigns cannot be deleted and will return an error.' Also suggests using replicate_campaign before deleting to preserve settings, giving clear when-to-use and alternatives.

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