douyin-top-account

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says the tool queries a ranking; it does not describe return format, pagination, permissions, rate limits, or whether the type parameter changes the result set. The single verb 查询 implies a read operation, but little else is disclosed.

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, front-loaded sentence with no wasted words; though '头部账号榜' and '最具影响力账号排行' are near-synonyms, the description is appropriately compact for a simple query tool. It would earn a 5 if it added a useful usage hint while staying 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?

Without an output schema or annotations, the description should compensate by explaining what the agent will receive and how parameters like type and dateType affect results. It does neither. The sibling list contains several similar Douyin ranking tools, and the description provides no context to disambiguate among them.

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 input schema already documents all three parameters (type, dateType, rankDate) with individual descriptions. The description adds no parameter-level meaning, but the schema does the heavy lifting, so the baseline of 3 is appropriate.

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 uses a concrete verb (查询) and a clear resource (抖音头部账号榜, 抖音最具影响力账号排行), so an agent can tell it queries a ranking of top Douyin accounts. However, it does not explicitly differentiate it from sibling Douyin ranking tools like douyin-rise-ranking or douyin-daily-hot, so it falls just short of a 5.

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 no guidance on when to use this tool versus alternatives. It does not mention that it is for influencer/account rankings rather than rising accounts or daily hot topics, nor does it reference sibling tools. The agent must infer applicability from the name alone.

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