douyin_search_videos

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the login prerequisite, that links are watermark-free and time-limited (几小时), and that the tool only returns URLs without persisting files. This is meaningful operational context an agent needs to act correctly, though it says nothing about rate limits or failure modes.

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?

Single dense paragraph with the core search purpose front-loaded, followed by return fields and the expiry caveat. Every clause earns its place, though the return-field enumeration is slightly list-like and could be trimmed.

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?

No output schema exists, so the description correctly enumerates the return fields (aweme_id, 文案, author, interaction data, watermark-free link) and adds the critical link-expiry caveat. Combined with the login requirement and follow-up routing, an agent has everything needed to call and use the result.

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 all five parameters (sort, count, account, keyword, publish_time) are already documented with defaults and enum meanings. The description adds no parameter-level detail beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb (搜索/search) and resource (抖音视频/Douyin videos) scoped by keyword, and explicitly differentiates from downstream siblings like douyin_video_detail and douyin_user_profile by naming what each returned id feeds into. An agent can identify this as the discovery entry point without opening any other tool.

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?

Gives clear context: it requires an active login, returns only addresses (不落盘), and routes follow-up work to douyin_video_detail and douyin_user_profile. It does not explicitly state when NOT to use it, but since no sibling competes as a search tool, the guidance is effectively complete.

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