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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds context by listing the aggregated signal types and implying a one-shot composite operation. However, it does not disclose output structure, data freshness, or any operational behavior beyond the annotation-covered safety profile.

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 a single dense sentence with no filler. It efficiently lists the many signals included in the package, making the scope clear. Slightly better structural separation (e.g., listing output items as bullets) could improve readability, but it is appropriately concise.

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 tool with no output schema, the description partially compensates by enumerating what the result contains (cross-platform resonance, trend curves, related terms, future signals, etc.). However, it lacks details on the output format or how these components are structured, which could leave an agent uncertain about how to parse the response.

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 parameters (keyword, geo, timeframe) are fully documented in the schema. The description does not add any parameter-specific meaning beyond what the schema already provides, meeting the baseline for full coverage.

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 identifies the tool as a comprehensive topic intelligence package that aggregates multiple data dimensions (cross-platform resonance, search trends, related words, future signals, etc.). This distinguishes it from sibling tools that focus on single aspects, though it does not explicitly name any sibling or contrast itself with them.

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 guidance is provided about when to use this tool versus alternatives. The statement '供大模型做定性/阶段判断/机会风险分析' gives a general use case, but it does not mention any sibling tools, exclusions, or selection criteria.

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