douyin_search_articles

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

No annotations are provided, so the description carries the full burden. It discloses that offset starts at 0 and increments by 20, explains sort_type default behavior, and mentions the return fields (total/hasMore/list). However, it does not describe mutation, rate limits, or authorization needs. The description is adequate given the absence of annotations.

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 with three packed sentences. Each sentence adds distinct value: purpose, key parameter details, and return structure. There is no filler or 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?

Given an output schema exists, the description does not need to detail return values. However, the tool lacks annotations, parameters have no schema descriptions, and the sibling tools suggest many search variants. The description covers basics but could better explain when 'sort_type' accepts specific values besides 'default' and whether the search is real-time or cached.

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 input schema has 3 parameters with 0% description coverage, so each parameter has no JSON-schema-level explanation. The description compensates well by specifying that keyword is required, offset is pagination starting at 0 with +20 step, and sort_type uses 'default' string. This adds meaning beyond the raw schema.

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 '搜索抖音作品（优质库）' meaning 'search Douyin works (high-quality library)', which identifies the tool's purpose. The differentiation from sibling tools is implied by the platform and content type (Douyin articles/works vs. users or other platforms).

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 indicates keyword is required and provides usage details for offset and sort_type, but it does not explain when to use this tool versus related tools like 'douyin_search_users' or 'douyin_search_ai_articles'. It gives pagination hints but lacks guidance about search context or alternatives.

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