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

Annotations declare openWorldHint=true and readOnlyHint=false, but the description adds nothing beyond that – no indication of result scope, coverage, latency, or why a 'search' is not read-only. It contributes zero behavioral context and offers no clarification of the surprising 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?

It is short, but it is under-specified rather than concise: the single fragment 'search API' consumes the title without conveying any actionable information. There is no front-loaded purpose an agent can act on.

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 no output schema and only minimal annotations, the description must explain what a search returns and how it differs from alternative search tools; it does neither. Nothing an agent needs to call it correctly is present.

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 documented 'keyword' parameter (max 1000 chars), so the schema already carries the parameter meaning. The description adds no syntax, format, or query-construction guidance beyond it, which is the expected baseline when the schema does the work.

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 'Web Search: search API' merely restates the tool name and title in tautological form. It implies a general web search on a keyword but gives no verb+resource specificity, and among hundreds of search siblings (nexscope_web_search, nexscope_data_ai_search_google_search, nexscope_amazon_search, etc.) it offers no differentiation.

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 alternative search tools, no prerequisites, and no exclusions. An agent has no basis to prefer it over nexscope_web_search or any domain-specific search sibling.

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