neuron_list_tabs

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does add context by mentioning 'platform detection and capture counts', but it does not clarify whether the operation is read-only, what exactly 'capture counts' means, or any side effects. The word 'List' implies safety but not explicitly.

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 that front-loads the action and resource, making it efficient and scannable. The trailing 'with platform detection and capture counts' is concise but slightly vague, which cost it a perfect score.

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 0-parameter tool, the description is mostly sufficient, but without an output schema, the agent is left guessing what 'capture counts' refers to and whether there are any side effects. A clearer statement of the return value or the meaning of 'platform detection' would complete the picture.

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 tool has zero parameters, so there is nothing for the description to explain. The baseline for a 0-parameter tool is 4, and the description does not need to add anything.

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 verb 'List' and the resource 'open Chrome tabs', making the core function unambiguous. It is distinct from sibling tools like neuron_open_tab, and the additional qualifier about platform detection and capture counts adds scope, though it is somewhat ambiguous.

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 usage context is implied by the phrase 'List open Chrome tabs' — an agent needing to see open tabs would recognize this tool. However, there is no explicit guidance about when to use this tool versus alternatives, or any exclusions.

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