select_page

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

The description discloses the precedence behavior ('Index takes precedence') and implies state change (selecting active tab). With readOnlyHint=false, it aligns with mutation. However, it does not detail side effects, error conditions, or auth requirements.

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 extremely concise: two sentences, minimal words, no redundancy. It is front-loaded with the verb and resource, making it efficient for agents to parse.

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?

Given the tool's low complexity and full schema coverage, the description adequately covers selection criteria and precedence. However, it lacks information on return values or behavior when no match is found, which could be helpful.

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% with brief descriptions for each parameter. The description adds clarity by grouping parameters and specifying precedence ('Index takes precedence'), which enhances understanding beyond 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 clearly states the verb 'select' and the resource 'active tab', with specific selection criteria (index, URL, title). It distinguishes from siblings like 'list_pages' (listing) and 'navigate_page' (navigation).

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 on when to use this tool vs alternatives like list_pages or navigate_page. The description only mentions precedence (index takes precedence) but lacks context on when this tool is appropriate or when to avoid it.

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