Pin or unpin a tab

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

The annotation only says readOnlyHint=false, so the description must carry the behavior, and it does: it discloses the concrete state change (icon-sized tab) and the protective interaction with "close others." It stops short of saying whether the pinned state persists across session restore or browser restart, which matters for a persistent-flag mutation.

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 short sentences, zero filler; the effect is front-loaded in parentheses before the secondary note about the context menu. Nothing could be removed without losing 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 2-parameter, no-output-schema toggle with a thin annotation, the description covers purpose, effect, reversibility, and UI equivalence. The remaining gap is persistence/lifecycle of the pinned state, which an agent might reasonably want before pinning at scale.

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 the boolean is fully documented ("true to pin, false to unpin"), as is the context default. The description adds nothing parameter-specific beyond the toggle semantics implied by "or unpin it again," so baseline 3 applies.

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 and resource ("Pin a tab... or unpin it") and immediately explains the observable effect: it "shrinks to an icon and stops being closed by 'close others'." That effect also distinguishes it from the tab-closing siblings like browser_close_other_tabs without the agent 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?

"This is the same state the tab context menu toggles" anchors it to a familiar UI action, and the effect implies the use case (keep a tab out of bulk-close operations). However, there is no explicit guidance on when to pin instead of, say, grouping or duplicating a tab, and no stated prerequisites or exclusions.

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