meta_ads_ad_rules_list

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

The description explicitly declares 'Read-only,' which is crucial for behavioral transparency given no annotations. It also lists return fields. However, it does not mention pagination behavior (e.g., how the limit parameter affects results) or potential error conditions, which would be helpful for agents dealing with large rule sets.

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?

Three sentences, each with distinct purpose: core function, return fields, usage guide. No fluff, front-loaded, and efficiently conveys all necessary information.

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?

For a list tool with two parameters and no output schema, the description covers purpose, return fields, and usage context. It is slightly lacking mention of pagination or error handling, but overall complete enough for its simplicity.

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% with clear parameter descriptions. The description adds minimal value beyond the schema: it reiterates the account_id default behavior (optional, falls back to credentials) and the limit's default/max, which are already in the schema. No new semantic insights are provided.

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 lists Meta Automated Rules and specifies the exact fields returned (id, name, status, specs, schedule). It distinguishes itself from sibling tools like meta_ads_ad_rules_create, meta_ads_ad_rules_delete, etc., by emphasizing its role in auditing and finding rule IDs.

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 states use cases: 'audit existing automation before adding new rules' and 'find a rule_id before disabling / deleting an old one.' This provides clear context for when to use this tool versus the other ad_rules tools, though it does not explicitly list when not to use it.

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