plugin_list_tabs

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

With no annotations, description carries full burden. It discloses the '[Disabled]' status, details return fields (tab IDs, URLs, titles, readiness status, connectionId with explanation), and filtering behavior. Could explicitly confirm read-only nature since annotations are absent.

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?

Four sentences with zero waste. Critical '[Disabled]' status front-loaded. Each sentence delivers distinct value: capability, return structure, usage guidance, and parameter behavior.

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?

Excellent completeness given no output schema exists. Description enumerates all return fields and explains connectionId semantics. Distinguishes from browser_list_tabs sibling and explains relationship to plugin tools ecosystem.

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 has 100% coverage (baseline 3). Description repeats the schema's explanation of optional plugin parameter behavior ('When called without a plugin argument...') but adds workflow context rather than new parameter semantics.

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?

Explicitly states the tool lists open browser tabs matching 'plugin's URL patterns' (distinguishing it from sibling browser_list_tabs), identifies the resource clearly, and prefixes with critical '[Disabled]' status.

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?

Provides explicit workflow guidance: 'Use this to discover which tabs are available before targeting a specific one with the tabId parameter on plugin tools.' Also clarifies behavior when parameter is omitted.

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