page_switch

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

With no annotations present, the description carries the full burden of behavioral disclosure, but it only states the action. It does not mention side effects (e.g., changing the active tab), behavior when the index is out of range, or any impact of the lease or session parameters. Minimal behavioral detail is disclosed.

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 and is front-loaded with the core action. It avoids filler and repetition, though it is slightly sparse; however, for such a simple action the length is acceptable.

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?

Although the schema describes all parameters, the tool is part of a large set of page/session tools and has lease and session conditions that an agent must understand to call it correctly. The description lacks operational context, and with no output schema or annotations, the agent is left without guidance on when or how to use this effectively among many similar tools.

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?

The parameter describing coverage is 100%, so the schema fully documents index, lease, and session. The description itself adds no parameter-level meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource, 'Switch to tab by index', which is clear and unambiguous. It distinguishes this from navigation tools (go/back/forward) by specifying index-based tab selection, though it does not explicitly name alternative siblings.

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 sibling tools like 'pages', 'page_new', 'page_close', or 'session_switch'. There is no mention of criteria such as having a tab index available or handling multiple sessions, leaving the agent to infer appropriate use from the tool name alone.

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