item.view

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

没有 annotations，描述承担了行为说明责任。它揭示了“浏览器视角”这一实现特征和“抗风控”这一风险相关行为，这些都无法从 schema 中获知。虽然未展开说明是否需要登录、权限或“抗风控”的具体限制，但“查看 / view”已经清楚暗示这是一次只读操作。

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?

对于只有一个必填参数且有输出 schema 的只读查看工具，描述已覆盖用途、行为特征和与 item.get 的区分点。由于没有 annotations，若能再补充登录要求或“抗风控”的具体含义会更好，但整体信息量已经足够支撑安全调用。

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 描述覆盖率为 0%，描述本身也没有补充 item_id 的含义或格式。不过该工具只有一个参数，参数名 item_id 和 schema 中的“Item Id”已经足够自明，且与“商品”语境吻合，因此没有造成实质混乱，但也没有提供额外语义。

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?

描述以明确动词加对象开头：“浏览器视角查看商品详情”，并直接与兄弟工具 item.get 做差异对比（“字段比 item get 更全”），还给出了“抗风控”这一识别特征。Agent 无需查看 schema 就能判断该工具的作用和独特价值。

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?

描述给出了相对 item.get 的选择依据：需要更全字段、需要浏览器视角或抗风控能力时，应使用 item.view。但没有明确说明何时应优先使用 item.get，例如对原始接口响应或更低调用成本有要求时，缺少显式排除条件。

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