update_campaign

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

No annotations are provided, so the description must carry the burden. It warns that launching requires an explicit yes, implying a destructive or state-changing operation. However, it does not disclose permissions, rate limits, or other behavioral traits. The warning is helpful but incomplete.

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 zero wasted words. The first sentence states the core purpose, the second provides critical usage instructions. 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?

Given the presence of an output schema, return values need not be described. The description covers the status parameter well but omits details about the name parameter. For a tool with 3 parameters and no annotations, more completeness on all parameters would be expected.

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 input schema has 0% description coverage, meaning the schema alone provides no parameter meaning. The description adds crucial semantics for the status parameter by listing valid values (ACTIVE, PAUSED, DELETED). It does not explain the name or campaign_id parameters, but status is the key parameter.

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 tool updates a campaign. The verb 'Update' and resource 'campaign' match the name. It distinguishes from siblings like update_ad and update_adset by focusing on campaigns. However, it does not elaborate on what fields can be updated beyond status and name.

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 on using the status parameter: 'Pass status ACTIVE to launch (get an explicit yes first), PAUSED to pause, DELETED to remove.' This tells when to use each status. No explicit alternatives are mentioned, but siblings are for different resources.

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