List Chrome tabs

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

No annotations are provided, so the description carries the full burden. It clearly conveys the read-only nature of the operation ('List'), discloses the output shape ('index + title'), and surfaces the notable multi-window behavior ('Operates on the first Chrome window'). This is solid behavioral disclosure for a simple list tool.

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 with no filler. The core action and return values are front-loaded, followed immediately by the key behavioral caveat. Every word earns its place.

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 zero-parameter, simple read-only tool, the description covers the essential context: what it lists, what is returned, and the first-window limitation. There is no output schema, so including the return format in the description is valuable and sufficient.

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 tool has zero parameters, and the baseline for no parameters is 4. There is no parameter schema to clarify, and the description does not need to add parameter semantics since none exist.

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 uses a specific verb ('List'), names the exact resource ('every open tab in Chrome'), and tells the agent what is returned ('index + title'). It also clarifies the scope limitation to the first Chrome window, which distinguishes it from generic tab operations and sibling tools.

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 when to use the tool—when the agent needs a list of Chrome tabs with indices and titles—and provides the important scoping rule about the first window. However, it does not explicitly name alternatives or state when not to use it, such as when another Chrome window's tabs are needed or when a tab action like open/close/focus is required.

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