list_adsets

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 does not disclose behavioral traits beyond the literal 'list' action, such as pagination behavior, default fields returned, permissions, rate limits, or response format. The description merely restates the tool's name and mentions filters already present in the schema.

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 a single, concise sentence that front-loads the main action and resource, followed by optional filter conditions. Every word earns its place with no redundant or filler content.

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 tool has 5 parameters and no output schema, and there are no annotations. The description covers the core function (listing ad sets) and optional filters, but it does not explain pagination behavior or what data is returned, nor does it differentiate from the closely related get_campaign_adsets tool. It is adequate for a simple list operation but leaves notable gaps.

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 all parameters have descriptions in the schema. The description adds minimal contextual value by noting that filters are optional, but it does not elaborate on how to use the pagination cursor, the limit parameter, or the fields parameter beyond what is in 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 action ('List ad sets') and resource ('in the ad account'), with optional filters by campaign or status. This distinguishes it from sibling tools like list_ads, list_campaigns, and get_adset, and the scope is explicit.

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 implies when to use the tool (listing ad sets with optional filters) but provides no explicit alternatives or exclusions. It does not mention when to use get_campaign_adsets or other related tools, so usage guidance is only implicit.

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