meta_ads_ad_sets_list

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

No annotations provided, so the description carries the full burden. It declares 'Read-only', lists returned fields, and explains that ad sets 'are where budgets and targeting live.' This adds context beyond the schema. However, it does not mention pagination, rate limits, or behavior with no results, which is a minor gap.

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, front-loaded with the core action and scope, then return fields, then usage. No redundant words. Every sentence serves a purpose. Excellent efficiency.

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 lists returned fields adequately. Without annotations, it covers read-only safety. It touches on use cases. Missing pagination details (though limit parameter exists) and account_id fallback behavior (covered in schema). For a simple list tool, it is mostly complete.

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%, so the baseline is 3. The description adds the phrase 'optionally scoped to a single parent campaign' which echoes the schema description for campaign_id. It doesn't add new information beyond confirming optionality. No extra semantics for account_id or limit beyond what the schema provides.

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 ad sets' with optional campaign scope, lists specific returned fields, and differentiates from mutation tools by stating 'Read-only' and usage as 'audit delivery settings' or 'find an ad_set_id before creating ads.' It distinguishes from siblings like meta_ads_ad_sets_get and create/update tools.

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 explicitly mentions optional campaign scoping and gives two concrete use cases. While it doesn't explicitly state when not to use it, the read-only declaration and context from sibling tools make usage clear. No explicit alternatives are named, but the purpose covers well.

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