Hide or show a tab in the tab strip

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

Annotations only say readOnlyHint=false, so the description carries the burden and does well: it discloses that a hidden tab stays loaded and remains reachable by context id, and that hiding the last visible tab is impossible. It does not state what happens on failure or what the call returns, which keeps it below 5.

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 action and its internal API mapping, then the usage note and the constraint. No filler and nothing redundant.

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 two-parameter, fully described schema with no output schema, the description covers purpose, side effects on tab state, and the blocking constraint. Only the error/response behavior on a refused hide is unaddressed, which is a minor gap.

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 100% and both parameters are already documented inline ('true to show it again, false to hide it', context defaults to the active tab). The description adds only a light hint that a hidden tab is reachable 'by context id', reinforcing the context parameter but not extending its semantics 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?

States a specific verb pair and resource: hide a tab from the tab strip (gBrowser.hideTab) or bring it back (gBrowser.showTab). The phrase 'park a tab without closing it' separates it from browser_close_tab and browser_pin_tab without needing to open either schema.

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?

Gives a clear use case ('handy to park a tab without closing it') and a hard precondition ('the last visible tab in a window cannot be hidden'). It stops short of explicitly naming the alternative tools (close_tab, pin_tab) that an agent might otherwise choose, so it is clear context rather than full when/when-not routing.

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