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

Annotations only supply readOnlyHint=false and openWorldHint=true, and the description adds nothing about pagination, rate limits, or what the query returns. It does not contradict the annotations, but it contributes zero behavioral context for a 29-parameter query.

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 single sentence is short but under-specified rather than concise; it conveys no information beyond the title and offers nothing front-loaded about filtering or results.

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 29-parameter store query with no output schema and thin annotations, the description should explain the store-research use case, filtering semantics, and return shape. It says nothing, leaving the agent wholly dependent on the schema.

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 29 parameters are documented in the schema itself. The description adds no parameter meaning beyond that, but baseline 3 applies since the 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?

The description restates the title: 'Temu Product Research: temu/store Query API' names a resource (Temu stores) but supplies no specific verb or scope beyond 'Query'. It doesn't differentiate from close siblings like nexscope_temu_store_source_query or nexscope_geekbi_temu_mall_search.

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?

No when-to-use, when-not-to-use, or alternative-naming guidance is provided. With dozens of Temu-adjacent sibling tools, the agent has no signal for choosing this one over nexscope_temu_store_source_query.

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