jd_search

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

由于没有任何注解，描述承担了全部行为透明责任。揭示了headless返回0结果、必须headful、登录profile要求以及并发串行化等关键行为。

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?

尽管存在浏览器自动化等复杂性，描述覆盖了核心使用上下文（登录、并发、headful需求）。输出模式存在，无需提及返回值。

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?

输入模式覆盖率100%，描述未为参数增添额外语义，基线3分合理。

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?

明确的动词+资源组合“搜索京东商品”，直接表明功能；与其他平台搜索工具（如taobao_search）明显区分。

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?

提供了详细的使用前提：需要headful Chrome、持久登录profile、首次手动登录以及并发保护（BrowserLock），但未明确说明何时不使用或替代方案。

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