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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the '[read]' prefix is largely redundant. The description adds the useful relational context about which tools consume the ids, but says nothing about pagination behavior or what the listing returns.

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?

One tightly packed sentence with the resource front-loaded and the disambiguating cross-references in a parenthetical. No wasted words.

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?

For a 4-parameter, all-optional read tool with annotations and no output schema, the description is adequate but thin: it never says what a negative keyword list contains or what the response looks like, and the filter parameters' accepted values are left entirely to guesswork. Enough to call it safely, not enough to call it confidently.

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?

With 0% schema description coverage, the description carries the full burden, and it only mentions 'scope or status' — echoing the parameter names verbatim without stating valid values, format, or semantics for those filters. The page/per_page parameters receive no mention at all, so the coverage gap is largely uncompensated.

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 the negative keyword lists') and disambiguates the concept by naming the two sibling tools that consume the returned id (add_negative_keywords, review_ads_search_terms). An agent can distinguish this from the many other list_ads_* siblings without opening any schema.

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 parenthetical explains the purpose-context in which to call this: to obtain the list id that add_negative_keywords and review_ads_search_terms take as input, and it notes optional scope/status filtering. It gives clear usage context but no explicit 'when not to use' or alternative-tool exclusion beyond the cross-references.

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