sessions_list

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

There are no annotations, so the description carries the behavioral disclosure burden. It indicates a read-only listing operation via 'Show', scopes results to currently running sessions on this machine, and links results to diagnostic uses. However, it does not explicitly state side effects, data freshness, or structural behavior beyond listing.

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 two sentences with no filler. The first sentence states what the tool does, and the second gives practical guidance, both earning their 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 zero-parameter listing tool with no output schema, the description provides a complete enough picture: what is returned (sessions and tabs) and when to use it. It does not detail the exact response shape, but that is less critical given the simplicity of the operation.

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?

This tool has zero parameters, so there is no schema burden. The description still clarifies what the returned data represents (sessions and their tabs), which is useful despite the 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?

The description uses a specific verb ('Show') and resource ('every DevCDP session currently running on this machine and the tabs each one holds'), making the tool's scope immediately clear. It also differentiates itself from sibling tools like list_tabs by emphasizing the all-sessions-on-machine view rather than a single context.

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 description explicitly provides two concrete use cases: understanding why a tab is unavailable and confirming whether two agents are fighting over the same page. It does not mention when not to use the tool or name alternative sibling tools, but the context is clear enough for an agent to select it appropriately.

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