wechat-channels-crawler

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

With no annotations, the description carries the disclosure burden. It reveals that the tool searches by keyword, supports multiple sort orders, and returns results as a structured table. However, it does not mention pagination behavior, data limits, freshness, or any constraints of the crawler.

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 well organized: it opens with the tool's core purpose, then explains supported behavior and output, followed by clear use cases and trigger words. The trigger-word list adds routing value without being overly verbose.

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?

There is no output schema and no annotation coverage, so the description must fully explain how to call the tool correctly. It leaves page/size semantics unspecified, does not map sort modes to parameter values, and only vaguely describes the return as a structured table.

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%, but each parameter description is tautological ('keyword', 'sort', 'size', 'page'). The description adds meaning for keyword and sort dimensions, but it does not specify exact sort values or the units/ranges for page and size.

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: searching WeChat Channels (视频号) works by keyword, with sorting modes and structured table output. It is distinguishable from generic wechat-search by focusing specifically on Channels video data, though it does not explicitly name sibling tools.

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 description provides explicit when-to-use scenarios: finding hot content, searching viral videos, querying video data, or understanding content performance on WeChat Channels. It includes trigger words to help route intent, though it does not state when not to use it or name alternatives.

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