wb_find_tab

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses that the tool 'Never navigates on failure' and that duplicate URLs require upstream ID support, but it omits whether selection activates/focuses the tab, what happens when the tab is missing, and how the session override behaves.

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?

Three short sentences, front-loaded with the core action, followed by failure behavior and the duplicate-URL constraint. No filler and no 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 four-parameter selection tool with no annotations and no output schema, the description covers the selection mechanism and failure behavior but is silent on state effects (does it activate the tab?), error semantics, and the role of the session parameter. It is adequate but leaves meaningful gaps.

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 description adds real meaning beyond the schema by explaining that tabId is 'resolved to unique URL' and that URL matching must be exact and unique. Schema coverage is 75% (tabId lacks a description), so this added context is valuable, though active and session are left entirely to 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 states a specific verb and resource ('Select a session tab') and explains the two addressing modes (exact URL or tabId resolved to unique URL). It is distinguishable from wb_list_tabs and wb_close_tab by implication, though it does not explicitly name those 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 duplicate-URL caveat ('Duplicate URLs require upstream ID support') gives a concrete condition for when URL-based selection fails, but the description never states when to use this tool versus wb_list_tabs or wb_navigate. Usage is implied rather than prescribed.

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