meta_ads_ad_sets_list

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

With no annotations provided, the description carries the full burden. It explicitly marks the operation as 'Read-only', which is a key behavioral trait. It also lists the exact fields returned. It does not mention pagination or rate limits, but the schema already documents the limit parameter, and the read-only disclosure is sufficient for safety.

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 two sentences, front-loaded with the primary action, and efficiently packs in returned fields and usage guidance. Every sentence earns its place, and there is no redundancy or filler.

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 is complete for a list tool: it explains the purpose, return fields, read-only nature, and use cases. The schema handles parameter details, and there is no output schema, so the field list is essential and provided. It could mention behavior with no results or pagination, but that is minor given the schema's limit description.

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 schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds minimal parameter semantics beyond what the schema already provides—it reinforces the optional campaign scoping, but does not introduce new meaning for the parameters.

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 ad sets in a Meta Ads account, with optional scoping to a single parent campaign. It enumerates the returned fields, and the verb 'lists' is specific to this read operation, distinguishing it from sibling tools like meta_ads_ad_sets_get or meta_ads_ad_sets_update.

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 gives explicit use cases: 'use this to audit delivery settings or to find an ad_set_id before creating ads.' It does not explicitly state when not to use it or name alternatives, but the context is clear enough for an agent to decide.

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