meta_ads_ad_rules_create

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

Despite no annotations, the description clearly discloses mutability, reversibility (rollback disables rule but actions stand), and return value (new rule_id). It also references Meta's API docs for full field details, adding transparency without contradictions.

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?

The description is concise: three sentences plus a list of common patterns. Key info (purpose, return, reversibility, common uses) is front-loaded. No unnecessary words or repetition.

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?

The description covers return value, parameter usage, and common patterns. It references external docs for full schemas and mentions rollback_apply as a related tool. It could note prerequisites (e.g., active account) but overall is fairly complete for a creation 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?

The input schema has 100% coverage, and the description adds extra context: naming convention, AND-logic for filters, OR for multiple rules, default schedule, and status staging. This enhances understanding beyond the basic schema descriptions.

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 creates a new Automated Rule, returns rule_id, and lists common patterns (CPA-spike alert, auto-pause ads, scale winners). It differentiates from sibling tools (e.g., view, list, update, delete) by focusing on creation and providing specific use cases.

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?

The description provides common patterns and reversible nature via rollback_apply, guiding when to use the tool. However, it lacks explicit exclusions or comparisons to alternative creation tools (e.g., meta_ads_campaigns_create), which would improve guidance.

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