get_adsets

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

No annotations are provided, so the description carries the transparency burden. It discloses meaningful behaviors: access_token caching fallback, pagination with per-page limit, and fetch_all for following cursors. This goes beyond the basic 'Get' verb and provides useful operational details.

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 extremely concise: one clear purpose sentence followed by a focused parameter list. Every line adds value, no fluff, and the structure is easy to scan.

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 tool's moderate complexity (5 params, output schema present, no annotations), the description covers purpose, all parameters, pagination, and auth fallback. It lacks explicit error conditions or rate-limit notes, but those are not critical for a listing tool with an output schema.

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 has 0% description coverage, so the description's Args section fully compensates by explaining each parameter: account_id format (act_XXXXXXXXX), access_token optionality/caching, limit default, campaign_id filter, and fetch_all pagination behavior. This adds substantial meaning beyond the schema's bare titles and defaults.

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 specifies the action ('Get'), the resource ('ad sets'), and the scope ('for a Meta Ads account with optional filtering by campaign'). It is clear and distinct from siblings like get_ads or get_adset_details, though it does not explicitly name 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?

The description conveys when to use the tool (to retrieve ad sets, optionally filtered by campaign) via the main sentence and parameter details. It does not explicitly contrast with sibling tools or state exclusions, but the usage context is clear.

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