meta_ads_ad_rules_update

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

Discloses mutation nature, reversibility via rollback_apply, and effect timing (next scheduled evaluation). With no annotations present, the description adequately covers key behavioral traits, though auth requirements and rate limits are omitted.

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 core purpose, then additional behavioral details. No extraneous information; every sentence is necessary and well-placed.

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 key aspects: mutation, partial update, reversibility, timing, and status usage. Lacks explicit mention of return value beyond 'returns the updated rule', but without output schema, this is sufficient. Could hint at prerequisite of rule existence.

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. The description adds value by emphasizing partial update (only supplied fields change). The status parameter's use for suspension is also clarified, providing context beyond the 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?

The description clearly states it updates an existing Automated Rule, emphasizing partial update and return of updated rule. Among siblings like meta_ads_ad_rules_delete and meta_ads_ad_rules_get, this tool is distinctly identified as an update operation for automated rules.

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 partial update behavior and advises using status=DISABLED for suspension instead of deletion. However, it does not explicitly compare to other sibling tools like create or delete for when to use this tool over alternatives.

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