find_underserved_niches

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

Annotations already declare readOnlyHint=true, so the tool's read-only nature is known. The description adds behavioral context: returns categories/subcategories only, never brands, ranked by private-label winnability using 2-year marketplace data. It does not contradict annotations. However, it lacks details on rate limits, pagination, or data freshness beyond what is implied.

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 description is well-structured: starts with a bold key phrase, then explains purpose, followed by usage guidance and sibling exclusion. It is not excessively long and each sentence adds value. Minor improvement could be more brevity in listing example queries.

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?

Given the tool has 21 parameters, no output schema, and minimal annotations, the description covers purpose and usage well but does not describe the output format or how to interpret results (e.g., ranking criteria, data fields returned). For a tool of this complexity, more detail on return values would enhance completeness.

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 only 43%, meaning many parameters lack descriptions in the schema. The description adds context for a few parameters (e.g., default price range 20-70, unhappy_shoppers bias) but does not elaborate on the majority of the 21 parameters. For a tool with low schema coverage, the description should compensate more.

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 clearly states it finds underserved niches (real subcategories) with genuine demand and room to compete, ranked by private-label winnability from 2-year marketplace data. It distinguishes from sibling tools that return brands, making the purpose specific and unambiguous.

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 description explicitly states 'This is the RIGHT tool for ANY niche-discovery question' and lists example queries. It also provides clear when-not-to-use guidance by naming sibling tools category_undercompeted_brands and find_undercompeted_brands that return brands instead. Additionally, it explains how to handle user-provided department names.

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