rnw_tabs_list

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

No annotations are provided, so the description carries the burden. It discloses the key behavioral trait that the tool operates on open browser tabs, but says nothing about permissions, whether it involves server round-trips, error modes when no tabs are open, or any side effects. Minimal but not misleading.

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?

Single front-loaded sentence with no waste. It's appropriately sized for a zero-parameter read tool, though it offers no additional context.

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 zero-parameter tool with no output schema or annotations, the description leaves return-format details implicit (e.g., what index means, output array structure). Adequate but with clear gaps in behavioral and output context.

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?

Zero parameters, so baseline is 4. The description appropriately states no filtering or scoping options, consistent with an empty input schema.

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?

Specific verb (List) and resource (open browser tabs) with scope ('all'). Clearly distinguishes from tab-management siblings like rnw_tabs_new, rnw_tabs_select, rnw_tabs_close by describing a read operation over existing tabs.

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?

Implies usage (enumeration of open tabs) but provides no explicit when-to-use context or routing to alternatives like rnw_tabs_select for acting on a tab. An agent can infer the purpose but isn't guided on when this versus other tab tools is appropriate.

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