meta_ads_ad_rules_update

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

Discloses mutation, reversibility, timing (next scheduled evaluation), and best practice for suspension. With no annotations, description fully covers behavioral traits.

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?

Five sentences, front-loaded with core action, no superfluous words. Efficient and structured.

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?

Explains return value, mutation effects, and suspension best practice. Missing output schema, but description covers enough context for a partial update tool with nested objects.

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 has 100% coverage for 7 parameters. Description adds value by noting account_id fallback and merge advice for evaluation_spec. Adds meaning beyond schema.

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?

Description clearly states 'Updates fields on an existing Automated Rule' with 'Partial update' and 'Returns the updated rule'. Distinguishes from sibling tools like meta_ads_ad_rules_create and meta_ads_ad_rules_delete.

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 guidance on partial updates, reversibility via rollback_apply, and recommends using DISABLED status instead of deletion. Could be more explicit about when to use update vs other operations, but context is clear.

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