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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds that this is a filtering/list capability consistent with those hints, but does not disclose pagination behavior, data freshness, rate limits, or output format beyond what annotations provide.

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?

The first sentence front-loads the purpose and supported metrics. Subsequent sentences list trigger keywords, which are slightly verbose but serve discoverability. Overall efficient with minimal waste.

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 71-parameter tool with no output schema, the description covers the core purpose and use cases sufficiently. It needn't explain return values given the schema handles parameters, but it could note the response structure or pagination behavior. Still adequate for an agent to understand when and how to call it.

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 100%, so all 71 parameters are fully documented in the schema. The description groups filter categories (price/rating/margin ranges, new product share, etc.) but adds no syntax or format details beyond what the schema already provides. Baseline 3 is appropriate when schema does the heavy lifting.

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?

States a specific verb ('filter') and resource ('Amazon niche markets by category dimensions') and lists supported metrics (market size, competition, seller structure, etc.). Clearly scoped to market-level filtering, though it does not explicitly differentiate from similar siblings like nexscope_amazon_opportunity_search_by_metrics or nexscope_amazon_niche_info.

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?

Provides explicit trigger conditions and use cases ('Trigger when the user mentions Amazon market research, niche category research, market opportunity screening...') and clarifies it applies even without the 'Nexscope' keyword. However, it offers no when-not-to-use guidance or alternative tool recommendations.

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