nex_browser_tab_list

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real value by disclosing that the response includes both the tab list and the active/stable page ID — a concept other tools depend on — but says nothing about behavior when the session is absent or about pagination/ordering.

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?

A single well-formed sentence with the return content front-loaded and zero filler. It is efficient, though it is terse enough that a short second clause about session requirements would have earned its place.

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 read-only, single-optional-param tool with no output schema, the description covers the essential contract: it lists tabs and the active stable page ID for a session. What is missing is how the IDs relate to tab_select/navigate and any behavior on an invalid session.

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?

Only one optional parameter with 100% schema description coverage, which already documents "Defaults to the active session." The description's "for an automation session" is consistent with the schema but adds no new semantics beyond it, so baseline 3 applies.

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?

States a specific verb ("List") and resource ("tabs") plus an extra return element ("active stable page ID"), all scoped to an automation session. This clearly separates it from mutating siblings like nex_browser_tab_new/select/close, though it doesn't name any sibling explicitly.

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?

There is no statement of when to call this versus alternatives (e.g. nex_browser_connection_info, nex_browser_snapshot), no preconditions, and no note on what to do with the returned page ID. Only the phrase "for an automation session" hints at context.

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