session_select_page

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

With no annotations, the description carries the full burden and does add useful behavioral context: the tool changes session state (active tab) and has a broad effect on all subsequent browser_* calls. This is the key behavioral trait beyond a simple read/write hint, and it 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?

Two sentences, front-loaded with the core action, then a concise dependency/scope note. No filler or repeated schema information.

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 one-parameter state-selection tool, the description covers what it does, how it affects browser tools, and where the parameter value comes from. The presence of an output schema covers return-value expectations, so nothing essential is missing.

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 coverage is 0%, but the description compensates by telling the agent exactly where to obtain page_id (session_list_pages or session_new_page). This adds actionable meaning beyond the bare 'page_id' string in the schema.

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 opens with a specific verb and resource ('Switch the active tab') and immediately explains the tool's role in the session: every browser_* tool acts on this tab. This clearly distinguishes it from session_new_page/list_pages/close_page and from the browser_* actions.

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?

It states the prerequisite source for page_id ('Take the id from session_list_pages or from session_new_page') and implies that selection should precede browser_* calls by saying those tools act on the active tab. It lacks explicit when-not/alternatives, but the contextual guidance is clear.

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