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

Annotations already declare readOnly=true, openWorld=true and destructive=false, and the description goes beyond them by warning that nullable fields mean missing evidence, that estimates are provider observations rather than real account performance, and that no retries or fallbacks occur. That is genuine behavioral context an agent needs before interpreting results, though it says nothing about result volume or ordering.

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?

It is short and the purpose clause comes first, so nothing is buried. However it is telegraphic to the point of ambiguity - four clipped fragments with no subject or verb in the opening clause - which costs clarity rather than saving space.

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 only hints at the return shape ('nullable fields', 'approximate ad counts'). Combined with completely undocumented parameters and no usage framing against ~20 sibling ad/keyword tools, an agent lacks enough to invoke this 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?

Schema description coverage is 0% for two parameters. The description never explains what 'query' matches against (advertiser name, domain, keyword?) or what 'limit' controls beyond the schema's own 1-20 bounds. With low coverage the description is expected to compensate and does not.

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 phrase 'advertiser directory matches, with approximate ad counts' identifies the resource and the returned metric, but it is a noun fragment with no verb, so it is unclear whether it searches advertisers, looks up an advertiser, or enumerates a directory. It also never distinguishes itself from close siblings like nexscope_seo_ad_transparency_search or nexscope_seo_ad_audience_estimate, leaving the agent to guess which one 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?

'No additional calls or fallback' is a constraint on execution, not guidance on when to pick this tool over the many SEO ad siblings. There is no stated precondition, no when-not-to-use, and no named alternative, so routing decisions get no help.

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