browser_navigate

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

无注释，描述仅说明'导航到 URL'，未披露任何副作用、是否需要等待页面加载、是否影响当前浏览器状态等。

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，需描述补充。

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%，两个参数都有描述；描述本身未额外解释参数信息。

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?

描述为 '导航到 URL'，明确了动词和资源，但与兄弟工具（如 navigate_back/forward）没有明确区分，只是通过 URL 暗示用于任意地址。

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?

没有任何关于何时使用此工具、何时使用替代工具的说明；没有提及像 browser_navigate_back 等兄弟工具。

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