douyin-search

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

无任何注解，描述需承担全部行为披露责任。'热门爆款作品'这一范围限定是有效的行为信息——说明这不是全量搜索而是热门内容搜索；日期筛选也是行为特征。但未说明结果排序规则、'爆款'的判定标准、翻页行为或调用限制。

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?

描述仅两个短句、无冗余修饰，核心动作和范围控制在前端。首句'抖音作品查询工具'与工具名略有重复，但作为领域锚点可接受；第二句承载了主要信息量，整体精炼高效。

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?

对5参数、无输出schema的工具而言，基本调用方式是明确的：关键词必填、日期可选、分页参数有默认值。但无输出schema的情况下描述未提及返回内容形态（如视频数据、作者信息、热度指标），也未说明'爆款'筛选逻辑，agent难以预判结果结构。

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描述覆盖率为100%，所有5个参数（keyword、startDate、endDate、pageNum、pageSize）在schema中已有说明。描述中'按日期范围筛选'只是重复schema已有信息，但'热门爆款'为keyword参数提供了一点语义上下文（搜索目标限定为热门作品），整体处于基准水平。

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?

描述包含具体动词（搜索）、资源（抖音作品）和范围限定（热门爆款、按日期筛选），能清晰传达这是关键词搜索工具。在众多抖音相关兄弟工具中（douyin-hot-trend、douyin-daily-hot、douyin-top-account等），关键词搜索这一特性将其与feed/榜单/账号类工具区分开，但未明确指出具体不同于哪一兄弟工具。

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?

描述完全没有提及何时使用此工具或何时使用替代工具。面对大量抖音内容探索类兄弟工具（douyin-hot-trend、douyin-content-surge、douyin-ai-feed等），agent无法获知关键词搜索与热门趋势/feed流工具之间的选择条件，也没有任何排除性说明。

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