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

Annotations already declare readOnly/openWorld/non-destructive, yet the description adds real behavioral context beyond them: the data is historical rather than live, domain filters act on cited sources while keyword filters act on answer text, and callers must preserve nullable evidence and unsupported dimensions. That is meaningful beyond what the annotations convey.

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?

Four short sentences with no filler, and the core behavior (ranked cited domains, no subdomain merge) is front-loaded. The final sentence about preserving nullable evidence feels like an instruction rather than a definition but is still compact.

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 tool with a nested target array (DOMAIN vs KEYWORD variants), no output schema, and no structured parameter documentation, the description should say more about what the ranked result contains (e.g., citation counts, ordering) and how the two target kinds combine. Historical-data and null-preservation notes help, but key gaps remain.

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% at the top level (only two nested field descriptions exist), so the description must compensate. It clarifies filter semantics (domain filters vs keyword filters map to cited sources vs answer text) and the no-subdomain-merge behavior behind includeSubdomains, but says nothing about limit, market, language, or platform values.

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 names a concrete verb and resource: ranked cited domains, explicitly without merging subdomains. That distinguishes it implicitly from nexscope_seo_ai_top_cited_pages and nexscope_seo_ai_top_mentioned_brands, but it never names or contrasts those siblings and 'provider ranked cited domains' is terse jargon an agent must decode.

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?

It gives a useful usage caveat that this is historical provider database data rather than a live model execution, which tells the agent when the answer is stale-safe. But there is no explicit when-to-use / when-not-to-use guidance and no routing to alternatives among the many seo_ai_* siblings.

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