meta_ads_ad_sets_list

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

No annotations are provided, so the description carries the full burden. It declares 'Read-only' but does not disclose other behavioral traits such as pagination behavior, rate limits, or result ordering. The schema covers the limit param's pagination details, but the description itself lacks this context.

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 four sentences long, starting with the main action, then listing fields, declaring read-only, and ending with use cases. Every sentence adds value; no wasted words. Well-structured and 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 the lack of output schema and annotations, the description covers the core purpose and use cases adequately. It lists returned fields and suggests practical applications. Minor gaps: does not mention default limit or error conditions, but the schema's limit description partially compensates.

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 description coverage is 100%, so the schema already documents all three parameters. The description adds minimal value by restating the campaign scoping option and listing returned fields, but does not provide new semantic insights 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 the tool lists ad sets in a Meta Ads account, optionally scoped to a campaign. It lists returned fields and distinguishes itself from mutation tools (create, update, pause) and sibling list tools (e.g., meta_ads_ads_list) by specifying the resource (ad sets) and noting it's read-only.

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 explicit use cases: 'audit delivery settings or find an ad_set_id before creating ads'. It does not explicitly exclude alternatives but the context makes it clear when to use this vs. mutation tools. Implied alternatives (e.g., meta_ads_ad_sets_get for a single ad set) are not mentioned.

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