meta_ads_ads_update

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

No annotations, so description carries full burden. Discloses mutating nature, partial update, and creative limitation. Does not warn about implications of status DELETED/ARCHIVED or permissions, but covers main behavioral traits well.

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 main action. No redundant info. Each sentence adds critical detail (partial update, creative limitation, status alternatives) without 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?

Covers main aspects: what it does, returns, cannot do, alternatives, reversibility. Lacks explanation of error handling or permissions, but given no output schema and no annotations, it is fairly 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%, baseline 3. Description adds value beyond schema by noting status should be handled via pause/enable and creative changes cannot be done. Account_id fallback not repeated but schema covers it.

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?

Clearly states it updates fields on an existing ad, partial update, returns updated ad. Distinguishes from siblings by specifying creative cannot be swapped and status-only transitions should use 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?

Provides explicit when-to-use and when-not: for status-only, use meta_ads_ads_pause/meta_ads_ads_enable; for creative changes, create replacement ad. Mentions reversibility via rollback_apply.

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