meta_ads_campaigns_update

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

Describes mutation and reversibility, but with no annotations, it could further detail authorization or rate limits. Still, it clearly states 'Mutating, reversible via rollback_apply' and 'Partial update'.

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?

Four sentences, front-loaded with core purpose, then adds key details; no unnecessary words.

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?

Comprehensive for an update tool: explains purpose, partial update behavior, return value, reversibility, and appropriate alternatives. No output schema needed as return is described.

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 100% with detailed parameter descriptions. The tool description adds context about partial updates but does not significantly enhance parameter meaning 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 it updates fields on an existing campaign, specifies it's a partial update, and distinguishes from sibling tools for status-only transitions (meta_ads_campaigns_pause/enable).

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 recommends using dedicated pause/enable tools for status changes and notes that the tool is mutating and reversible via rollback_apply, providing 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.