list_sessions

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

The description discloses the key behavioral trait: completed sessions are automatically cleaned up when listed. No annotations exist, so the description carries the full burden. It adds value by noting this side effect, though it could mention if the operation is safe or has rate limits.

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 sentences with front-loaded purpose and no unnecessary words. Every sentence provides essential information about the tool's function and side effects.

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 tool with an output schema, the description covers the core purpose, displayed fields, and cleanup behavior. It is complete enough, though additional details about ordering or limits are not necessary given the simplicity.

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?

No parameters exist (schema coverage 100%), so baseline is 4. The description adds meaning by explaining what is displayed and the cleanup behavior, which enriches the empty 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 clearly states it lists active process sessions ('Lista todas las sesiones de proceso activas') and shows specific fields (PID, command, status, etc.). It implicitly distinguishes from sibling tools like list_processes by focusing on 'sessions' from start_process.

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?

While the description mentions sessions from start_process, it does not explicitly state when to use this tool versus alternatives like list_processes or read_process_output. Usage context is implied but not directly guided.

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