list_ad_sets

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

With no annotations, the description carries full burden; it does declare read-only safety and the "recent" scoping plus configured-account constraint, which is valuable. However, it omits pagination behavior, ordering, and what the response contains.

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, safety qualifier and usage hint front-loaded, zero waste.

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?

A simple single-param read tool is adequately framed for purpose and usage, but with no output schema the description should hint at returned fields/pagination, and it leaves the lone parameter undocumented.

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?

One parameter (limit) exists at 0% schema description coverage, and the description never mentions it. The tool has params, so the zero-param baseline of 4 doesn't apply; the agent gets no guidance on default or meaning of limit.

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?

States a specific verb and resource ("List recent ad sets") scoped to the configured Meta ad account. It's clearly distinct from list_campaigns and list_ads by resource, though it doesn't explicitly contrast with siblings.

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?

"Use this to find ad set IDs before budget or status changes" gives explicit context for when to call it. No exclusions or named alternatives, but the usage scenario is clear.

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