ruyi_list_pages

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

The description clearly states the tool's behavior: listing all open tabs. With no annotations, the description carries the full burden, and 'list' inherently implies a read-only operation with no side effects. It is sufficient for a simple list tool, though it does not mention any additional details like sorting or formatting.

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?

The description is a single, concise sentence in Chinese (translated as 'List all open tabs'). It is front-loaded with the core action and contains no unnecessary words or 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?

For a tool with no output schema and no annotations, the description does not explain what information is returned for each tab (e.g., ID, title, URL). This is a gap because an agent would need to know how to correlate list results with actions like select_page. Otherwise, the simplicity of the operation makes it mostly complete.

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?

There are zero parameters, so the description need not explain parameter semantics. The schema coverage is trivially 100% (empty schema). Baseline for 0 parameters is 4, and the description adds nothing beyond what is already clear.

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?

The description '列出所有打开的标签页' (List all open tabs) uses a specific verb ('列表/list') and clearly identifies the resource (open tabs/pages). It differentiates from siblings like select_page, new_page, and close_page by its listing function.

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?

No explicit guidance is provided on when to use this tool versus alternatives such as select_page or new_page. The context that it lists open tabs is implied but there are no stated use cases, prerequisites, or exclusions.

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