标签页列表

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

无任何注解，描述自行声明“只读操作”，提供了安全/副作用方面的关键信息。但未说明返回格式、排序、空标签页列表行为，或是否包含标签页 ID，行为透明度有限。

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 且无注解，描述应更完整说明返回结构。虽然提到 URL 和标题，但未涉及标签页唯一标识或返回形式，对后续切换等操作可能不够充分。

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 参数基线评分为 4。

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 与标题。这与打开、关闭、切换标签页等兄弟工具明显区分，目的清晰。

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?

描述没有说明何时使用该工具、何时不使用，或指出与 web_tab_new、web_tab_switch 等工具的关系。仅凭“列出全部标签页”间接暗示用途，缺少明确的场景指导。

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