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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds scope context (Reddit/community discussions, external posts, trending topics, real-time data) beyond the annotations, but says nothing about result volume, freshness window, pagination, or ranking.

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?

A single comma-separated keyword list repeats 'web search', 'online retrieval', 'real-time information', 'search engine' and 'trending topics' multiple times. The actionable trigger rule arrives only in the final sentence, after the bloat, so the definition is back-loaded rather than front-loaded.

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 one-parameter search tool with strong annotations, the description covers the what and a rough when. It is missing whatever would most help an agent actually use it (typical result shape, freshness behavior, whether community sources are always included), which matters more given there is no output schema.

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 coverage is 100% with a single required 'keyword' parameter already documented (including the 1000-character limit). The description adds no meaning beyond the schema, so the baseline 3 applies; notably it gives no guidance on whether to phrase the keyword as a natural-language question or as query terms.

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 verb+resource is identifiable ('web search', 'online retrieval', 'real-time information query'), but it is buried in a synonym pile covering the same single action. Nothing distinguishes it from the many sibling search tools such as nexscope_data_ai_search_google_search, nexscope_google_ai_mode_search, nexscope_data_search_search, or nexscope_seo_serp, which an agent will also consider.

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?

The closing sentence gives real trigger guidance ('trigger whenever intent involves obtaining real-time web information or verifying current facts'), including the implicit-intent case. However, no when-not condition and no named alternative among the numerous sibling search tools, so routing decisions remain guesswork.

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