meta_ads_ads_update

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

With no annotations provided, the description carries full burden. It discloses mutation, partial update nature, reversibility via rollback_apply, and creative swapping limitation. While it doesn't cover authentication or rate limits, it provides key behavioral traits for decision-making.

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?

Three short sentences plus one important note. Front-loaded with core purpose. Every sentence adds value with no redundancy.

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?

Covers purpose, usage boundaries, return value, and mutation traits. Lacks error conditions or permissions, but for a 4-param tool with explicit schema and no output schema, it is sufficiently complete.

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%, so baseline is 3. The description adds context about partial update (only send fields to change) and the rollback capability, which enriches understanding beyond the schema parameter descriptions.

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 an existing ad, specifies it's a partial update, and explicitly distinguishes from siblings by noting creative swapping requires a different approach and status transitions should use pause/enable tools.

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 when not to use this tool: for status-only transitions (directing to meta_ads_ads_pause/meta_ads_ads_enable) and for creative changes (requiring creating replacement ad). This clearly sets boundaries among siblings.

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