list_collection_videos

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

With no annotations present, the description carries the full behavioral burden but discloses almost nothing: no read-only confirmation, no authentication/login prerequisite (notable given the douyin_login_start/logout siblings), no pagination or rate-limit behavior. 'List' weakly implies a safe read, but that is inference, not disclosure.

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 efficient sentence with the resource and scope front-loaded and zero filler. It is appropriately sized, though the brevity comes at the cost of the missing usage and behavioral detail noted elsewhere.

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?

This is a low-complexity, zero-required-parameter read tool with a fully documented schema and no output schema, so the description need not explain return values. Still, given the dense sibling set and absent annotations, the lack of any authentication or collection-scoping note leaves a modest gap.

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%: limit and cursor are both documented in the schema, so the description is not required to explain them. It adds no syntax or default-value detail beyond the schema, making the baseline 3 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 states a specific verb (List) and resource (videos) and even scopes it to the default Douyin 'favorite' collection, which tells an agent this is the fixed favorite collection rather than an arbitrary one. However, it does not explicitly name or distinguish itself from the closely related siblings list_collects and get_collect_videos, leaving the agent to infer the boundary.

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?

There is no explicit when-to-use guidance, no exclusions, and no mention of the alternative get_collect_videos for non-default or specified collections. The only implicit signal is 'default ... favorite collection', which a careful agent could use to route, but nothing is stated.

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