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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered and the description adds the useful context that these are trending queries from the app search box. However, it calls itself a 'no-argument list', which misrepresents the actual call behavior given the schema exposes two optional parameters — a mild behavioral inaccuracy.

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?

Two tight sentences, front-loaded with what the tool returns and followed by when to use it. No filler, though the 'no-argument' phrasing is wasted/misleading space rather than pure padding.

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?

An output schema exists, so return values need not be explained, and the discovery-oriented framing is adequate for a simple list tool. The remaining gap is the unexplained scene/word_type parameters plus the 'no-argument' claim that leaves the agent unsure whether any parameters are usable.

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 0% for both parameters (scene, word_type), so the description carries the full burden — and instead of compensating it claims the tool is a 'no-argument list', actively steering the agent away from two real parameters. The description adds no semantics for scene or word_type and contradicts their existence.

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 — fetching trending search keywords surfaced in SHEIN's app search box — which is concrete and distinct from generic catalog search. It does not name any sibling tool, so the agent must infer that shein_products_search is the downstream alternative, which keeps it below a 5.

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?

It gives clear usage context: use the list to discover popular shopping queries *before* searching the product catalog, which implicitly positions shein_products_search as the follow-up tool. No explicit exclusions or when-not-to-use conditions are stated.

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