douyin-content-surge

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

No annotations are provided, so the description carries the full disclosure burden. It only signals read-only behavior through '查询' and does not describe what the returned ranking contains, how surge is computed, whether startDate is necessary, or any response-shape details.

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 compact sentence that leads with the resource and follows with the purpose. It is appropriately brief, though the brevity comes at the cost of behavioral and contextual detail.

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?

With no output schema and no annotations, the description should at least characterize the returned data and ranking behavior. It does not explain what fields are returned, how the date parameter affects results, or how this surge ranking behaves relative to other ranking tools, leaving an agent with significant gaps.

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 schema already documents the type options and the startDate format. The description adds no parameter-specific meaning, which matches the baseline of 3 for fully covered parameters.

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, the Douyin content surge ranking, and a concrete action: querying viral content with surging interaction data. It is clear and read-oriented, though it does not explicitly distinguish itself from closely related siblings such as douyin-weekly-surge or douyin-rise-ranking.

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 implies a use case but gives no explicit guidance on when to use this tool versus alternatives. With many sibling ranking tools present, there is no when-to-use or when-not-to-use guidance to help an agent route correctly.

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