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

With no annotations, the description carries full burden and delivers genuine behavioral detail: it discloses that Meta pads results with unrelated filler that this tool strips, and that supplying special_ad_category restricts results to approved interests only. It stops short of noting auth requirements, result count/pagination behavior, or rate limits, so not a full 5.

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?

Front-loaded with the what/coverage before the how-to-consume details; each sentence carries operational content (mapping, filler removal, special ad category, audience sizing). Slightly dense and could be trimmed, but nothing is wasted.

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?

There is no output schema, and the description compensates by explaining the result shape (each item has a `type`) and the example payload. Combined with the 4-param schema, an agent has enough to call and consume it correctly, though nothing is said about result ordering or what an empty result means.

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 75%, so baseline is 3, but the description adds real meaning: it explains the semantic effect of special_ad_category (approved interests only) and ties a returned field (`type`) to how each item must be keyed downstream. The `limit` parameter is left untouched.

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?

Specific verb 'Search' + resource 'Meta detailed targeting', explicitly enumerating the three categories (interests, behaviors, demographics) it unifies. This distinguishes it from the near-named siblings adsap_search_interests and adsap_search_behaviors, which cover only one category each.

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?

Gives concrete downstream usage: place each result under its `type` key inside a flexible_spec group of adsap_create_ad_sets, and route the same groups to adsap_get_delivery_estimate to size the audience. Also states the conditional rule for when to pass special_ad_category. Little is left to inference.

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