browser_tab

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Manage tabs' reveals no behavioral traits: it doesn't say whether the action is destructive, whether it requires a session, what side effects occur, or what the response contains. This is entirely opaque for a tool with multiple actions.

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 short, but this is under-specification rather than conciseness. It lacks structure such as action enumerations, parameter grouping, or usage examples. The single vague phrase does not help the agent understand the tool.

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?

This is a 5-parameter tool with a required action, no output schema, and no annotations. The description is wholly inadequate – it gives no information about valid actions, required fields, session handling, or return values. An agent cannot correctly invoke this tool based on the provided definition.

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%, so the baseline is 3. The description adds no meaning beyond the schema – it does not explain how parameters relate or what actions they enable. However, the schema does provide per-parameter descriptions, so the description does not need to compensate.

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 'Manage tabs' is vague – it states a resource (tabs) but not a specific action. It lacks the specificity needed to distinguish this tool from siblings like browser_open or browser_navigate, which also deal with tab-like operations. It does not indicate whether the tool creates, closes, switches, or lists tabs.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any use cases, prerequisites, or exclusion conditions. An agent would have no basis for choosing this over other browser tools.

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