list_sessions

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

No annotations are provided, so the description carries the full behavioral burden; it implies a read-only operation by using 'List' and specifying 'active' sessions but does not state whether it requires an active connection, what the return format is, or whether it can be called before any session exists. For a zero-parameter read tool, this is adequate but incomplete.

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, front-loaded sentence with no wasted words. It is appropriately sized for a zero-parameter tool.

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 simplicity of a zero-parameter list tool and the absence of an output schema, the description is minimally sufficient but does not explain what constitutes an 'active' session, the return shape, or whether it requires an existing connection. More context would help the agent use it correctly alongside session-management siblings.

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?

There are no parameters, so the baseline is 4. The schema is empty and the description correctly does not introduce any parameter details, keeping it aligned.

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 states a clear verb (List) and resource (active Electron testing sessions), which distinguishes it from siblings like close_session and get_page_info. However, it does not explicitly differentiate itself from connect_to_electron_cdp or launch_electron_app, which also relate to sessions, so it is clear but lacks sibling differentiation.

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 guidance on when to use this tool versus alternatives such as get_page_info or get_main_window_info, nor any exclusions or conditions. The agent must infer that this lists sessions rather than acting on them.

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