Activate or pause a Meta campaign

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

Annotations (readOnlyHint=false, destructiveHint=false) indicate mutation but no destruction. The description adds critical behavioral context: starting real ad spend on activation, requiring confirm flag, and safety of pause. No contradiction with 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?

Description is dense but efficient. Front-loaded with purpose, then usage rules. Could be slightly more structured (e.g., bullet points), but every sentence earns its place.

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 3 params with full schema and output schema exists (context shows has output schema:true), the description covers all needed aspects: parameter roles, activation guardrails, permission. Return values are covered by 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?

With 100% schema coverage, baseline is 3. The description adds value by explaining 'ACTIVE = start spending' and 'PAUSED = stop', and emphasizes the confirm parameter's role in activation approval. CampaignId is tied to create_meta_campaign.

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 'Turn' and the resource 'campaign ON/OFF', with clear mapping to ACTIVE/PAUSED. It distinguishes from sibling tools like create_meta_campaign or meta_insights.

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 says when to use (activate/pause), and more importantly, provides a mandatory precaution for activation: must show user campaign name + budget, get explicit yes, then call with confirm:true. Also mentions 'Pausing is always safe' and 'Needs ads-management permission'.

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