zen_tabs

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

The description implies a read-only operation without explicit state modification. Since no annotations are provided, the description carries the burden, and it adequately conveys the tool's non-destructive nature. However, it could explicitly state that no state is changed.

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 sentence, no wasted words, directly front-loaded with the verb 'List'. Perfectly concise for the information it conveys.

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?

Given the tool's simplicity (no parameters, no output schema), the description is largely complete. It covers purpose and output. Missing details like whether all windows are included could be added, but the current level is 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?

With zero parameters and 100% schema coverage, the baseline is 4. The description adds value by specifying exactly what fields (IDs, titles, URLs) are returned, which is beyond the empty 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?

The description 'List all open browser tabs with their IDs, titles, and URLs' clearly states the action (list), resource (tabs), and specific output fields. It distinguishes from siblings like zen_page_info or zen_close_tab by focusing on listing all tabs rather than acting on one.

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?

No guidance is given on when to use this tool versus alternatives like zen_switch_tab or zen_page_info. The description does not specify prerequisites or exclusions, leaving the agent to infer usage from context alone.

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