list_sessions_tool

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

With no annotations, the description carries the full disclosure burden. It communicates a read-only listing action, but does not disclose return format, pagination, session-state filtering, or whether it covers all sessions in the workspace. This is minimally adequate for a simple list operation but thin.

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 concise sentence with no filler. The scope modifier 'in the workspace' adds useful context and is front-loaded effectively.

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 operation, the description is nearly complete. The lack of an output schema and any mention of returned session fields or defaults leaves a minor gap, and the existence of get_status creates mild ambiguity about which tool answers which session-related need.

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 the baseline of 4 applies. There is no parameter information to add beyond what the empty input schema already shows, and the description does not need to compensate.

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 and resource ('List sessions') and adds a workspace scope. The verb 'list' distinguishes it from action-oriented siblings like run_session, create_session_tool, step_session, and stop_session, though it does not explicitly point to any alternative.

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?

No guidance is provided on when to use this tool versus get_status or the other session-related siblings. There are no exclusions, conditions, or alternative suggestions, leaving the agent to rely on naming inference.

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