browser_tabs

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

Annotations already indicate a destructive, open-world tool. The description adds the action list but discloses no additional behavioral traits like reversibility or side effects of closing/selecting tabs.

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?

One sentence, perfectly front-loaded, with zero filler. It directly states the purpose.

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 multi-action tool with a complete schema and annotations, the brief description is adequate, though it does not describe return values for the list action or edge cases like omitted index for close. Still, given the simplicity, it's mostly complete.

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 input schema provides full descriptions for all three parameters with 100% coverage, so the description adds no extra semantic detail beyond listing actions. Baseline 3 is appropriate.

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 specifies four concrete operations (list, create, close, select) on browser tabs, clearly identifying a resource and a set of verbs. It distinguishes from sibling tools by focusing on tab management rather than navigation or page interaction, though it doesn't explicitly contrast with browser_close.

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 guidance is provided about when to use this tool versus browser_navigate or browser_close, and there are no stated conditions or alternatives. The description simply lists actions, leaving the agent to infer context.

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