meta_ads_ad_rules_list

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

Declares the tool as read-only, which is key behavioral info. However, no annotations are provided, and the description omits details like pagination behavior, rate limits, or authentication requirements beyond the fallback mention in parameter docs.

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?

Two sentences: first states purpose and output, second gives usage guidance. No superfluous words, information is front-loaded.

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?

Given no output schema, the description adequately summarizes return fields (including schedule and spec summaries). Does not detail the format of evaluation_spec/execution_spec, but 'summary' implies non-exhaustive. Still sufficient for a list tool.

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%, and the description adds value by explaining the optional account_id fallback and the default/max for limit, providing context beyond the schema's minimal 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 'Lists Meta Automated Rules' and enumerates the returned fields (id, name, status, evaluation_spec summary, execution_spec summary, schedule). It differentiates from sibling tools like meta_ads_ad_rules_get by focusing on listing all 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?

Explicitly provides two use cases: auditing existing automation before adding new rules and finding a rule_id before disabling/deleting. Implicitly contrasts with related tools by mentioning 'before adding', 'disabling / deleting'.

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