douyin_search

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

With no annotations, the description fully carries the burden. It reveals critical behavioral details: CDP browser automation, auto-polling, captcha waiting for manual intervention, and automatic result capture. This transparency helps an AI agent understand the tool's interactive nature.

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 extremely concise—three sentences, each earning its place: purpose, prerequisite, and behavior. It is front-loaded with the core action and uses no unnecessary words.

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?

Given the lack of annotations and the presence of an output schema, the description covers necessary context: functionality, prerequisites, and user interaction. It could mention pagination or error handling, but overall it is sufficiently complete for a search tool.

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 baseline is 3. The description does not add additional meaning for the 'keyword' or 'limit' parameters beyond what is already in the schema, thus not improving parameter understanding.

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 explicitly states '搜索抖音视频' (search Douyin videos), clearly identifying the verb and resource. It distinguishes from sibling tools like douyin_comments, douyin_hot_list, and douyin_video by focusing on search 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 provides clear prerequisites: Chrome must be logged into Douyin via guided_login. It also explains that the tool will wait for manual captcha resolution. However, it does not explicitly contrast with alternative search methods or state when not to use this tool.

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