List Ad Sets

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description does not need to repeat that. The description adds some context like pagination via 'after' cursor, but does not explain behavior like rate limits or confirmation of results. It adds marginal value beyond annotations.

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 concise with bullet-like arg listing, front-loads the purpose, and every sentence adds value. No unnecessary words.

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 lacks information about return format (despite response_format parameter in schema) and pagination details beyond the cursor. For a list tool without output schema, these are gaps. The description is adequate but incomplete.

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 description adds meaning by clarifying the relationship between campaign_id and ad_account_id ('Provide either'), and lists status_filter enum values. However, it misses the response_format parameter which is in the schema. With 50% schema coverage, the description compensates well but not completely.

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, with the specific context of filtering by campaign or ad account. This distinguishes it from sibling tools like meta_list_ads or meta_get_adset.

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 explains the key usage rule: provide either campaign_id or ad_account_id. It also lists optional filters. However, it does not explicitly state when not to use this tool (e.g., for a single ad set use meta_get_adset) or mention alternatives.

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