meta_ads_ads_update

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

With no annotations, the description carries full burden. It discloses mutability, non-reversibility, partial update behavior, and return value. It adds valuable context about creative limitations and rollback logging. Minor gap: no mention of permissions or error conditions, but overall strong transparency.

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 earning its place: purpose, partial update/return, mutability/rollback, creative limitation, and status alternatives. Information is front-loaded and no filler exists.

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?

For a mutating tool with no output schema, the description is remarkably complete. It covers return value, rollback concern, creative change path, and alternative tools for status transitions. Given the 4 parameters and 100% schema coverage, nothing critical is missing.

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 the baseline is 3. The description adds meaningful semantics: account_id falls back to META_ADS_ACCOUNT_ID, and status changes should prefer pause/enable tools. This exceeds schema descriptions by clarifying optionality and preferred usage for specific parameters.

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 opens with 'Updates fields on an existing ad. Partial update.' – a specific verb and resource with a clear scoping qualifier. It differentiates from sibling tools by explicitly naming meta_ads_ads_pause/meta_ads_ads_enable for status-only changes and by stating that creative cannot be swapped via this call, which distinguishes it from creation 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 to use this tool versus alternatives: status-only transitions should use pause/enable, and creative changes require creating a replacement ad. It also advises recording before-state with mureo_state_action_log_append for rollback, giving practically actionable context.

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