neuron_session_list

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

No annotations are provided, so the description carries the full burden. It indicates read-only behavior through 'List', defines the scope ('all active sessions'), and discloses the output content ('progress summaries'). It does not discuss side effects, but none are expected from a list operation.

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?

Two short, focused sentences: the first states the action and return content, the second gives usage context. There is no redundancy, no filler, and the key information is front-loaded.

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 low-complexity, parameterless tool with no output schema, the description is complete. It specifies what the tool returns, the scope of results, and when it is useful. Nothing essential is missing for an agent to call it correctly.

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 and the schema covers 100% of nothing, so there are no parameter semantics for the description to add. This matches the baseline for a parameterless tool.

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 specific verb ('List'), a clear resource ('sessions'), and a scoped qualifier ('all active sessions'). It also specifies what is returned ('progress summaries'), making the tool's purpose immediately identifiable and distinct from session-related siblings like save, load, delete, or checkpoint.

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 gives two practical use cases: resuming interrupted work and cleaning up stale sessions. It does not name alternative tools or exclusion criteria, but for a zero-parameter list operation this is sufficient contextual guidance for an agent.

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