douyin_search_videos

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value by specifying that only public videos passing page status and relevance checks are returned, which is beyond the annotation. The read-only trait is also confirmed in the description, aligning with the annotation.

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, concise sentence that front-loads the action and includes essential filtering behavior. There is no wasted text or unnecessary repetition.

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?

The tool is relatively simple, but the description omits any mention of the return format, pagination, or how the limit and relevanceThreshold parameters affect results. Without an output schema, more detail would be needed for a fully self-contained description. The 'page status' reference is also vague.

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 0%, and the description does not elaborate on any parameters. While the parameter names (keyword, limit, relevanceThreshold) are somewhat self-explanatory, the description fails to define 'relevanceThreshold' or explain how 'page status' relates to the search. The description's mention of 'relevance checks' provides minimal linkage but does not compensate for the lack of parameter documentation.

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 clearly states the tool searches keywords on Douyin's video search page and returns only public videos that pass page status and relevance checks. This is a specific verb+resource combination that distinguishes it from sibling tools like douyin_inspect_video or douyin_list_commented_videos.

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 when to use this tool: when a search by keyword is needed. It does not explicitly mention alternatives or exclusions, but the context of searching on the video search page is clear. Since no other sibling tool covers search, it is sufficiently differentiated.

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