search_videos

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

No annotations are provided, so the description carries the behavioral burden. It clearly states that the tool searches and returns a dict with a video list, which is core behavior, but it does not disclose authentication requirements, rate limits, pagination behavior beyond parameter defaults, or error conditions. This is adequate but not rich.

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 well-structured with a one-sentence purpose, a clean Args list, and a Returns line. Every line adds useful information and nothing is redundant or wasteful.

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?

All six parameters are semantically documented and the return type is stated, so an agent can invoke the tool correctly. Minor gaps remain around usage boundaries relative to sibling tools and any authentication or rate-limit caveats, especially given there are no annotations to provide safety context.

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%, but the description fully compensates by explaining every parameter: keyword, offset, count with max, search_channel with allowed values, sort_type with meaning, and publish_time with filter ranges. This adds significant meaning beyond the bare 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 opens with a specific verb and resource: 'Search for Douyin videos by keyword.' This makes the tool's purpose immediately clear and distinguishes it from sibling tools like get_homefeed, get_video_detail, or get_user_posts, which serve different retrieval needs.

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 keyword-based search purpose implies when this tool should be used, but the description provides no explicit guidance about when to prefer it over alternatives or when not to use it. For example, it doesn't mention that get_video_detail is for a single video or get_homefeed is for feed browsing.

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