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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only "RETURNS: 研究空白清单" — a useful hint about output kind, but nothing about depth, sourcing, or limits for a read-only analysis tool.

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 keyword-block structure is front-loaded and scannable, with the USE WHEN and RETURNS lines in predictable slots. The alias list is long but serves a real routing purpose for bilingual triggering.

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?

This is a simple two-parameter read-only tool with no output schema, and the description gives trigger, aliases, and the return kind. An agent has enough to call it correctly; only output granularity is left implicit.

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% with only two parameters (topic and population), both documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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 resource and action ("Research gap mining / 研究空白分析") and the USE WHEN line clarifies it identifies what is still unknown in a field. It conveys enough to separate it from adjacent siblings like topic_novelty or topic_feasibility, though it does not explicitly name or contrast those siblings.

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 USE WHEN clause gives a concrete trigger ("the user asks what is still unknown in a field, where the gap is"), which is clear routing guidance. It stops short of exclusions or naming alternatives, so it earns a solid 4 rather than a 5.

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