ruyi_select_page

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

With no annotations provided, the description carries the full burden of explaining behavioral traits. It merely says 'switch active tab' without disclosing side effects (e.g., changing the current working page for other ruyi tools), error behavior for invalid indices, or whether it focuses the browser window. This is a significant gap for a state-changing operation.

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, front-loaded sentence with zero wasted words. It conveys the core purpose immediately and efficiently, earning full marks for conciseness and structure despite being minimal.

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 one parameter, no annotations, and no output schema, the description is too sparse to be complete. It lacks essential context about how the active tab selection affects subsequent operations, the need to call ruyi_list_pages first, and potential error conditions. The schema covers the parameter but not the operational context.

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 description coverage is 100% (pageIdx is described as '标签页索引'). The description adds no additional meaning beyond the schema, so the baseline of 3 applies. The parameter's role is clearly defined in the schema, but the tool description does not elaborate on how the index maps to tabs.

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 '切换活跃标签页' (switch active tab) clearly states a specific action on a specific resource. It distinguishes itself from sibling tools like ruyi_list_pages (list), ruyi_new_page (create), and ruyi_close_page (delete) by focusing on selecting/activating an existing tab.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., existing pages), relationship to ruyi_list_pages for obtaining the index, or scenarios where one would choose this over ruyi_navigate_page.

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