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

Annotations already cover read-only/non-destructive/open-world, and the description adds genuinely new context: historical data rather than live model output, signed values, cited-source provenance for domain filters, and the instruction to "preserve nullable evidence and unsupported dimensions" (i.e. expect nulls and absent metrics). However, it never says what gets measured, how deltas are computed, or how "independent values" should be interpreted, so the disclosure is suggestive rather than actionable.

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, but the front-loading is wasted: the lead sentence is the least comprehensible one. Terseness here reads as under-specification rather than efficiency.

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, 4-required tool with no output schema, the description omits what the response looks like (delta magnitude? direction? per-dimension?), how groupRange shapes the series, and what distinguished platform=chat_gpt from google. An agent could construct a call but could not predict or interpret the result.

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%, so the description must compensate. The sentence "Domain filters use cited sources and keyword filters use answer text" does add real meaning to the DOMAIN vs KEYWORD target variants beyond the schema, and "preserve nullable evidence" warns about return semantics. But dateFrom/dateTo, groupRange granularity, platform (google vs chat_gpt), market and language get no explanation at all.

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 opening sentence, "Provider adjacent timestamp deltas with signed independent values," is dense jargon that never plainly states what the tool returns (AI mention change metrics over a date range). Compared with siblings like nexscope_seo_ai_mention_history or nexscope_seo_ai_mention_new_lost there is no differentiation, so an agent cannot confidently pick this over them. The name carries most of the meaning, which is the definition of a tautological-ish description.

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?

"Historical provider database facts, not a live model execution" hints at the data's nature but gives no when-to-use rule, no prerequisites, and never names an alternative among the many seo_ai_* siblings. The agent is left to infer that this is for period-over-period delta analysis rather than a snapshot query.

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