list_adsets

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

No annotations are provided, and the description says nothing about behavioral aspects like pagination, return format, rate limits, or required permissions. It only restates the basic action of listing ad sets, which provides no additional transparency beyond the name.

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, focused sentence that fully states the core purpose without any unnecessary words. It is optimally concise for a simple listing tool.

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 optional parameters, no output schema, and no annotations, yet the description provides no context about the ad account structure, filtering options, or list behavior. The description is far too minimal to be considered complete for this complexity level.

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 0%, and the description does not explain any of the five parameters (after, limit, fields, ad_account_id, effective_status). The description adds zero value for understanding how to use 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 identifies the tool as listing ad sets for an ad account, using a specific verb ('list') and a clear resource ('ad sets'). It distinguishes from siblings like list_campaigns and get_adset by resource name, but doesn't explicitly contrast with alternatives.

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?

There is no guidance on when to use this tool versus alternatives such as get_adset or list_campaigns. The description provides no context about prerequisites, typical scenarios, or exclusions, leaving the agent to infer usage from the tool's name and sibling names.

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