meta_ads_ads_update

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

No annotations exist, so the description carries full behavioral disclosure burden. It states 'Mutating — not automatically reversible; record before-state...' and explains that the creative cannot be swapped. This is clear and helpful, though it does not mention potential side effects like ad re-approval or delivery delays.

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?

The description is three sentences, front-loading the purpose, then mutability warning, then limitations and alternatives. Every sentence is substantive and contributes to understanding. No fluff.

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?

With no output schema, the description returns 'Returns the updated ad' which is adequate. It covers rollback, creative limitation, and status alternatives. However, it does not detail what fields are returned or mention potential approval triggers on field changes. Slightly more detail on return shape or side effects would push to 5.

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 parameters are well-documented. The description adds value by clarifying that 'status' parameter should ideally be handled via pause/enable tools, and it reinforces the creative limitation. This context beyond schema merits a score above baseline.

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 explicitly states 'Updates fields on an existing ad. Partial update.' It clearly identifies the verb (update) and resource (existing ad). It distinguishes from siblings by noting that creative swapping requires creating a new ad and that status-only 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?

The description provides explicit when-to-use (updating ad fields) and when-not-to-use (creative swaps, status-only transitions) guidance. It recommends using meta_ads_ads_pause / meta_ads_ads_enable for status changes and suggests recording before-state for rollback via mureo_state_action_log_append.

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