meta_ads_ad_rules_update

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

Discloses mutation, reversibility via rollback_apply, and that changes take effect on next scheduled evaluation. With no annotations provided, description fully covers behavioral traits, even noting partial update behavior.

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 short, front-loaded sentences with no fluff. Each sentence adds unique value: purpose, partial update, returns, mutation/reversibility, scheduling, status 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?

Covers mutation, reversibility, timing, partial update, and status guidance. No output schema needed; description sufficient. Lacks error handling info but acceptable for straightforward update.

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 description coverage is 100%, so baseline is 3. Description adds minor context like partial update hint and status usage advice, but parameters are already well-documented in 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 it updates an existing Automated Rule, specifies partial update semantics, and returns the updated rule. Differentiates from create/delete by focusing on update verb.

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 using DISABLED status for suspension instead of deletion to preserve history. Implies partial update behavior. Lacks explicit 'when not to use' or comparison with siblings like meta_ads_ad_rules_delete.

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