douyin_search_ai_articles

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

With no annotations provided, the description must fully disclose behavioral traits. It describes a search operation that likely involves network requests and potential rate limiting, but it does not mention any destructive or read-only behavior, data freshness, or pagination behavior. The note '（优质库）' hints at a curated dataset but lacks clarity.

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 concise, using only two sentences with no extraneous fluff. Key information is front-loaded in the first sentence. It could be slightly more structured by separating the required/optional sections textually.

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 presence of an output schema and 5 parameters, the description is incomplete. It does not explain what the output contains (e.g., a list of articles, metadata), how pagination works, or how the time filters interact with the curated dataset. More detail is needed for effective use.

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?

The description adds value by specifying the keyword as required and illustrating the datetime format for start_time/end_time. However, with 0% schema description coverage, the meaning of page_num and page_size is left implicit, and the description does not explain the effect of these parameters for pagination.

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 that the tool searches for Douyin AI-related works using a keyword, which is a specific verb and resource. However, it does not distinguish itself from the closely related sibling 'douyin_search_articles', which may cause confusion.

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 some usage guidance by indicating that 'keyword' is required and specifies the date format for start_time and end_time. However, it does not explain when to use this tool versus alternatives like 'douyin_search_articles', 'xiaohongshu_search_ai_articles', or other platform-specific search tools.

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