douyin-weekly-surge

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, but it offers only a single claim: it queries surging viral content for the week. It does not disclose what the ranking type parameter variations produce, how startDate interacts with the '本周' claim, output shape, pagination, or any rate-limit/auth considerations. Too thin for an unannotated tool.

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 efficient sentence with minimal waste, front-loading the ranking name and then the clarifying query statement. The opening '抖音周突增榜' slightly mirrors the tool name, but the second clause earns its place by specifying the resource and surge/interval criteria.

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?

Despite being a simple two-parameter tool, key context is missing: the meaning and valid values of 'type', the relationship between startDate and the stated 'this week' behavior, and any differentiation from siblings. With no output schema to cover return values, the description should explain more about what constitutes the returned '爆款内容' and ranking semantics.

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. Both parameters have descriptions, with startDate's format clearly stated and the description's '本周' adding loose context for date relevance. However, 'type' remains vague ('榜单类型' with a default of '2' but no enum or value explanations), and the description does not clarify which types exist or what '2' means.

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 ('查询'), resource (本周互动数据突增的爆款内容 — this week's viral content with surging interaction data), and temporal scope ('本周' weekly), making the core function clear. However, it does not explicitly differentiate itself from closely related siblings like douyin-content-surge or douyin-rise-ranking, whose names imply overlapping functionality.

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 choose this tool over the many similar Douyin ranking siblings (douyin-daily-hot, douyin-hot-trend, douyin-rise-ranking, douyin-content-surge). Usage context is only implied by the word '本周' — there is no when-not-to-use guidance or explicit alternative routing.

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