列出标签页

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

注解已声明 readOnlyHint=true，描述未添加额外行为信息，如返回格式、排序规则或可能的影响。由于注解已覆盖只读性，描述未进一步披露任何超出注解的细节。

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?

工具简单，仅有单个可选参数，且有输出模式，基本信息足够。但缺少使用场景和参数说明，整体略不完整。

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?

模式中定义了可选参数 browser_id，但描述未解释其用途。由于 schema 覆盖率为0%，描述本应补偿参数语义，但完全未提及，仅依赖参数名推测。

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?

描述明确指出动词“列出”和资源“所有标签页”，目的清晰。虽然未明确区分于其他标签页工具，但功能本身明确，且与 tab_info 等单个标签页工具有明显区别。

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?

描述仅说明功能，未提供何时使用、何时不使用或替代工具的建议。虽然用途隐含，但缺少明确的场景说明和与其他工具（如 tab_info）的选择依据。

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