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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description contributes one genuinely useful piece of context — that results come from a metrics pool aggregated from historical business insight reports, implying non-live, pre-aggregated data — but says nothing about result volume, empty-result behavior, or data staleness.

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?

What the tool does is front-loaded in the first sentence, followed by routing triggers. The long synonym list is keyword-dense but functional for skill selection, and the final sentence adds a real semantic fallback rather than repeating the list verbatim.

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 59-parameter tool with no output schema, the description never indicates what a result record contains or how many dimensions are returned per niche, leaving the agent to infer the response shape. Annotations and the very rich schema cover safety and inputs, but the output side is undocumented anywhere.

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%, so the baseline is 3, but the description earns extra credit by grouping the 59 parameters into navigable families (market size & growth, price tiers & share, competition density & top concentration, demographics, review highlights & pain points). That grouping helps an agent plan a filter combination before reading individual property docs.

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 names a specific verb and resource ('filter Amazon niches and keywords by 30+ business dimensions') and enumerates the dimension families, so an agent can tell this apart from a generic product search. It does not explicitly contrast with the closest sibling, nexscope_amazon_opportunity_report_by_keyword, which would have made the distinction airtight.

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 trigger list is unusually explicit ('Trigger when users mention reverse product selection, metrics filtering, niche reverse lookup, blue ocean niche discovery...'), and the closing sentence extends it to semantic intent even when the phrase is absent. There is no when-NOT-to-use guidance or named alternative for the case where a user wants a single-niche report instead of a filtered list.

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