fanqie_hotwords

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

There are no annotations, so the description carries the full behavioral burden. It does disclose that the tool uses a '套路词表' and performs frequency statistics, which is useful. Yet it omits details about return values, aggregation behavior, or any side effects, leaving important behavior unexplained.

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 compact single sentence with no filler. It front-loads the core function and then adds a usage-oriented summary, making it easy to scan; every part contributes meaning.

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 annotations, no output schema, and three undocumented parameters, this description is incomplete. An agent would still be guessing what 'rank' values mean, how 'top' behaves, and whether results differ across channels, so the definition is not sufficient for correct invocation.

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%, and the description does not explain any of the three parameters: 'top', 'rank', or 'channel'. The enum values like 'read' and 'new' are ambiguous without clarification, and the description does not compensate for the missing schema documentation.

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 action ('频次统计' / frequency counting) and target resource ('书名热词' / hot words in book titles). It also specifies the basis ('基于套路词表'), making it fairly specific among sibling tools, though it does not explicitly differentiate itself from 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?

The phrase '快速看当前书名流行词' implies this tool is for quickly viewing currently popular book-title words, giving some usage context. However, it provides no explicit when-to-use or when-not-to-use guidance and does not mention any sibling alternatives.

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