wechat-channels-ai-feed

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses meaningful behavior: daily automatic scanning, engagement-based filtering, clustering, HTML report generation, cover images, metrics, and daily subscription. It does not discuss side effects or output structure, but the described behavior is substantial and non-misleading.

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 well-structured sentence that front-loads the core function, lists key features, and ends with explicit usage triggers. Every part earns its place, and there is no redundant or filler wording.

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?

The description conveys the tool's high-level behavior and use case, but with no output schema and no parameter semantics, an agent still has to infer how to supply keyword, pageNum, and pageSize. It also does not explicitly contrast this tool with very similar siblings such as wechat-channels-crawler or the other ai-feed tools, leaving some selection ambiguity.

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 the baseline is 3. However, the schema descriptions are near-tautological ('keyword', 'pageNum', 'pageSize'), and the tool description adds no parameter-specific guidance about what keyword should contain or how pagination interacts with the daily report. The parameter names are self-explanatory to a degree, but the description does not enrich them.

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 states a specific verb and resource: it automatically scans WeChat Channels for AI-related works, filters by engagement metrics, clusters them, and generates an HTML daily report. This makes the tool's purpose concrete and distinguishes it from generic siblings like wechat-channels-crawler or platform-specific feeds such as douyin-ai-feed.

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 trigger conditions: use when the user needs AI video account daily reports, AI hotspots from video accounts, AI video account content, or a video account information source. It does not explicitly name alternatives or when not to use, but the context is clear enough for an agent to select this tool.

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