get_adsets

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

No annotations are provided, so the description carries full burden. It mentions optional access_token caching and default limit behavior, which adds some context. However, it lacks critical details: whether this is a read-only operation, potential rate limits, authentication requirements beyond the token, pagination for results beyond the limit, or error handling. For a tool with 4 parameters and no annotation coverage, this is insufficient.

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 front-loaded with the core purpose in the first sentence, followed by a structured Args section that efficiently explains each parameter. Every sentence earns its place with no redundant or vague language, making it easy to scan and understand.

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 4 parameters, 0% schema coverage, no annotations, but an output schema exists, the description does well by explaining all parameters and the tool's purpose. However, it lacks behavioral context (e.g., read-only nature, rate limits) and doesn't hint at output structure, though the output schema mitigates the latter. For a retrieval tool with sibling alternatives, more usage guidance would improve completeness.

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%, so the description must compensate. It provides clear semantics for all 4 parameters: account_id (format specified), access_token (optional with caching behavior), limit (default and purpose), and campaign_id (filtering role). This adds significant value beyond the bare schema, though it doesn't detail format constraints beyond account_id or explain empty string default for campaign_id.

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 verb 'Get' and resource 'ad sets for a Meta Ads account' with optional filtering by campaign. It distinguishes from siblings like 'get_adset_details' (specific ad set) and 'get_campaigns' (different resource), but doesn't explicitly contrast with 'get_ads' or 'search' tools that might also retrieve ad-related data.

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 usage through the optional campaign filtering parameter, suggesting this tool is for retrieving ad sets, possibly filtered. However, it doesn't explicitly state when to use this vs. alternatives like 'get_adset_details' (for a specific ad set) or 'search' (for broader queries), nor does it mention prerequisites beyond the required account_id.

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