Resume Campaign (gated mutation)

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

Annotations already indicate idempotentHint=true and destructiveHint=true, but the description adds only 'GATED' without explaining the gating mechanism or other behavioral traits (e.g., required auth, state prerequisites). The term 'GATED' is vague.

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 a single sentence of 9 words, front-loaded with the action and resource. Every word earns its place with 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?

For a mutation tool with destructiveHint=true and an output schema, the description is too brief. It lacks prerequisites (campaign must be paused), explanation of 'GATED', and expected behavior. The output schema exists but description does not complement it.

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 only 25% (only customer_id has a description). The tool description does not elaborate on any parameter, leaving parameter meanings unclear beyond the schema.

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 'Resume (enable)' and the resource 'a paused campaign by id'. It distinguishes from sibling tools like pause_campaign and resume_keyword by specifying the campaign context.

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 'GATED' implying special access conditions, but does not explicitly state when to use this tool versus alternatives. No comparison with siblings like resume_keyword or pause_campaign.

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