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

With only readOnlyHint=false and openWorldHint=true declared, the description adds real value by stating the data is historical provider database facts rather than a live model execution, and that new/lost counts are separate nonnegative values. It says nothing about pagination, limits, or why a statistics tool would be non-read-only, which leaves the annotation profile unexplained.

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 padding, and the core purpose is front-loaded. The closing line ('Preserve nullable evidence and unsupported dimensions') reads more like an instruction to the caller than a description of the tool, which adds slight ambiguity but little wasted length.

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 7-parameter tool with 0% schema coverage, sparse annotations, and no output schema, the description leaves most input semantics and the response shape undocumented. An agent would have to guess the meaning of groupRange, platform, and the date range before it could call this correctly.

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% across 7 parameters, so the description must carry the burden and largely does not. It clarifies the DOMAIN vs KEYWORD variants of `target` (cited sources vs answer text), but dateFrom, dateTo, groupRange, platform, market, and language receive no explanation beyond what the schema types already show.

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 resource ('new and lost mention statistics') but describes it in terms of data-retention semantics rather than a clear verb + scope. It does not distinguish this tool from close siblings such as nexscope_seo_ai_mention_deltas, nexscope_seo_ai_mention_history, or nexscope_seo_ai_mention_records, so an agent cannot tell which of the four 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?

There is no statement of when to use this tool versus the many sibling AI-mention tools, and no prerequisites or exclusions. The only usage-adjacent content ('domain filters use cited sources and keyword filters use answer text') explains filter behavior, not tool selection.

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