List Chrome Tabs

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

With no annotations, the description must disclose behavioral traits, but it only states that it lists tabs. It does not explain what 'available' means (e.g., includes internal tabs), whether it is read-only, or any side effects. The parameter includeInternal hints at a behavior but is not addressed.

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 sentence with no unnecessary words, front-loading the core action and resource. It earns its place and is highly concise.

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?

Despite the tool's simplicity, the description is incomplete. It lacks context on the CDP endpoint, the meaning of includeInternal, and the return format (no output schema). The absence of annotations further reduces completeness, as the agent cannot determine safety or behavioral implications.

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 schema has one parameter (includeInternal) with 0% description coverage, and the tool description does not mention this parameter at all. The description fails to add any meaning to the parameter, forcing the agent to guess what 'internal' refers to in the context of Chrome tabs.

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 with a specific verb 'List' and a distinct resource 'Chrome tabs available through the configured CDP endpoint'. This distinguishes it from sibling tools like select_tab or page_info, which perform different actions.

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 no guidance on when to use this tool versus alternatives. It does not mention scenarios, prerequisites, or contrast with sibling tools such as select_tab or page_info, leaving the agent to infer usage context.

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