wechat-fastest-growing

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

With no annotations, the description carries the full burden. It discloses useful behavioral constraints—daily updates and the 30-day window—but it does not describe output ordering, result fields, or behavior for invalid dates. Since there is no output schema, this leaves some uncertainty about the returned structure.

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?

A single compact sentence communicates the resource, the query method, update frequency, and time restriction with no filler. It is well-structured and front-loaded.

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 low-complexity, one-parameter read-only ranking tool, the description plus schema is sufficient for an agent to know what to call and how to pass rankDate. Slightly more detail about the returned ranking fields would make it fully complete given the absence of an output schema.

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%, and the schema already documents the date format, the 30-day limit, and the yesterday/today aliases. The description only restates date-based lookup and the 30-day restriction, adding no new parameter meaning beyond the schema.

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 names a specific resource—公众号阅读增长最快账号榜 (WeChat official account reading-growth ranking)—and a clear query mode (按日期查询). This distinguishes it from sibling tools like wechat-top-account and wechat-10w-hot, since it is specifically about accounts with the fastest reading growth.

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 gives clear usage context: query by date, updated daily, and only supports the last 30 days. It does not explicitly name alternatives or state when not to use the tool, so it stops short of a 5.

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