chrome_tabs

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

With no annotations provided, the description carries the behavioral burden. It discloses that the tool returns tab ids, that those ids are intended for sibling tools, and that sibling tools often default to the most recent tab. It does not discuss device targeting or side effects, but for a list-style read operation, the key behavior is covered.

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 two sentences with no filler. It leads with the core action and immediately follows with the most useful operational detail about ids and defaults.

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 simple listing tool, the description covers the essential behavior, the relationship to sibling tools, and the default-tab behavior. The main omission is device parameter semantics, but given that the parameter is optional and an output schema exists, this is a minor gap rather than a blocking one.

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 only parameter, device, has 0% schema description coverage and is not explained in the description. The phrase 'on the phone' hints at a default device but does not clarify how to select a specific device or how the empty default is resolved. The description does not compensate for the missing schema documentation.

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 action 'List' and the resource 'tabs open in Chrome on the phone.' It is immediately distinguishable from sibling tools like chrome_open, chrome_navigate, and chrome_close_tab, so an agent can understand exactly what this tool does.

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 provides practical guidance by explaining that the returned ids should be used with the other chrome_ tools, and that most of those tools default to the most recent tab. It does not explicitly list exclusions, but the purpose and typical workflow are clear enough.

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