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

With annotations present, the bar is lower, and the description does add real context: data provenance (historical database, not live execution) and the fact that domain filters match cited sources while keyword filters match answer text. It is silent on result shape, ranking metric, pagination, and — notably — does not reconcile the informational framing with readOnlyHint=false.

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, front-loaded with the data source, so it is compact. But several are terse fragments dense with unexplained jargon ("provider brand taxonomy", "Preserve nullable evidence and unsupported dimensions") that cost reading effort without returning meaning.

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 read query with a complex nested oneOf target parameter and no output schema, the provenance disclaimers are valuable, but the agent still does not know what a returned mention record contains, what ranks the brands, or why readOnlyHint=false on what appears to be a retrieval call. Adequate but leaves real gaps.

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 near zero for the top-level parameters, yet the description supplies the single most important semantic: DOMAIN targets are matched against cited sources and KEYWORD targets against answer text, which disambiguates the oneOf target structure. It says nothing about limit, market (US-only), language, or platform, leaving residual gaps.

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?

It names the resource (ChatGPT brand mentions with provider brand taxonomy) and clarifies the data is historical database facts rather than a live model call. But the operation itself — returning a *ranked top-N list* of brands — is never stated, and that is exactly what distinguishes it from siblings like nexscope_seo_ai_mention_records or nexscope_seo_ai_top_brand_categories.

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 a selection condition versus live-model tools such as nexscope_seo_model_answer_observation, but no when-to-use statement, no exclusions, and no named alternatives are given. Nothing tells the agent why to pick this over mention_records, mention_history, or top_brand_categories.

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