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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety burden is light. The description adds context annotations cannot: the response contains ids and names only, with no metrics, which matters because many sibling tools return performance data. It omits pagination, result caps, and search behavior.

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?

Two short sentences, front-loaded with the resource and platform terminology. The second sentence largely restates the first, so there is minor redundancy, but nothing is padded or vague.

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?

With no output schema, the description correctly takes on the job of describing return contents (ids and names, no metrics), which is the most important missing piece. For a four-parameter listing tool that is only about adequate: result limits, pagination, and the semantics of `search` remain unexplained.

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 50%: ad_account_id and platform are documented in the schema, while search and campaign_id have no description there. The description compensates partially by explaining the campaign scoping option and the ad-account scope, but says nothing about what `search` matches or how platform selection interacts with the ad account.

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 uses a specific verb and resource ("List the ad sets of an ad account") and even maps the concept across platforms (TikTok ad groups, Snapchat ad squads), so an agent knows exactly what entity is returned. It does not distinguish itself from the closely named sibling get_adsets, leaving ambiguity about which of the two to call.

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 phrase "optionally of one campaign" implies the campaign_id narrowing case, which is useful contextual guidance. However, it never states when to prefer this over get_adsets, list_ads, or list_campaigns, and gives no prerequisites beyond the implicit need for a connected account.

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