tabs

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It lists actions (list, new, select, close) but does not describe side effects, what 'select' or 'close' does to the current tab, whether actions are reversible, or what the output for 'list' looks like.

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 a single, concise sentence that is front-loaded with all key actions. It is efficient with no wasted words.

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?

The tool has four distinct actions and three parameters, yet the description is minimal. It does not specify return values (e.g., what 'list' returns), prerequisites, or behavior nuances like whether 'new' opens a foreground/background tab. Given the lack of output schema and annotations, this is insufficient for an agent to use the tool correctly without additional guessing.

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 67% with action having an enum and url/index having brief descriptions. The description adds no further parameter meaning, such as which combinations of action and parameters are valid. It provides a baseline but does not compensate for the missing 33%.

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 clearly states the tool's function: 'List, open, select or close tabs.' It uses specific verbs and identifies the resource (tabs), making the purpose unambiguous and distinct from sibling tools like 'goto' or 'open'.

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 description implies usage for tab management but does not explicitly state when to prefer this tool over siblings or provide exclusions. For example, it does not clarify whether 'open' should be used for URLs instead of the 'open' sibling tool.

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