meta_ads_ad_sets_update

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

Without annotations, the description fully discloses behavior: partial update, mutating nature, reversibility via rollback_apply, and the full replacement of targeting. This provides sufficient transparency for safe usage.

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, each essential. No redundancy, front-loaded with purpose, and structured logically: purpose, update behavior, reversibility, and special guidance.

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?

While the description covers key aspects (partial update, reversibility, targeting warning, status alternatives), it does not detail the return structure beyond 'Returns the updated ad set,' which is acceptable but could add slightly more detail given the absence of an 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?

Schema coverage is 100%, and the description adds significant value beyond the schema by explaining that targeting replaces the entire spec, status changes are better handled by dedicated tools, and daily_budget is only valid when campaign is not using CBO.

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 set, specifies partial update behavior, and distinguishes from sibling tools like meta_ads_ad_sets_pause and meta_ads_ad_sets_enable by noting they are preferred for status-only transitions.

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 guides when to use alternative tools (pause/enable for status changes) and provides a warning for targeting replacement with a specific recommendation to fetch and merge client-side, including the tool name meta_ads_ad_sets_get.

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