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

Annotations declare readOnly=false, openWorld=true, idempotent=false, destructive=false, but the description adds meaningful behavioral context the annotations cannot convey: cache hits under 7 days return instantly without consuming quota, and fresh analyses take minutes. This quota/latency disclosure is exactly the kind of added value that justifies a high score; error/auth behavior is not covered, so it stops short of 5.

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?

Four tight sentences, front-loaded with what the tool does, then outputs, then cache/quota, then latency. No filler; each sentence carries distinct information.

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?

With no output schema, the description correctly enumerates the return shape (clusters, keywords, opportunity scores, intent type, app concept suggestion) and covers caching and latency. It stops short of noting whether analyses persist or how results are retrieved later, which list_niche_analyses implies. Largely complete for a 4-param pipeline tool.

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% and includes careful guidance (e.g., the lang/country distinction, store enum values), so the schema does the heavy lifting. The description only implies the 'topic' input and adds no syntax or format detail beyond the schema, making the baseline 3 appropriate.

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 states a specific verb and resource and unpacks the full pipeline: discovers keywords, clusters into sub-niches, scores each cluster's opportunity. This distinguishes it from sibling tools like run_autocomplete or list_niche_analyses, which do not perform clustering/scoring. An agent can tell what it produces without opening the schema.

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?

Usage is implied by the pipeline description, but there is no explicit when-to-use guidance nor any named alternative or exclusion (e.g., versus run_autocomplete for keyword discovery). The cache/quota note informs expectations rather than routing. Adequate but with a clear gap in directive guidance.

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