parseltongue_list_sessions

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

No annotations are provided, so the description carries full behavioral disclosure burden. It merely states what it returns ('JSON with list of sessions') but doesn't disclose whether sessions are sorted, paginated, what session fields are included, or whether this is a read-only operation. The 0-parameter tool has the safety profile entirely unaddressed.

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 extremely short and front-loaded with the purpose. The Returns section is slightly redundant with the 'List all active sessions' line and could arguably be trimmed, but there's no waste given there's no parameter content needed.

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 this is a simple 0-parameter list operation with an output schema present, the description is reasonably complete. However, given no annotations and an empty input schema, the description could still add value by disclosing behavioral traits like whether sessions are ordered, how many are returned, or how to interpret the list. It's minimally adequate but leaves the return semantics open.

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 0 parameters with 100% schema coverage, so there's nothing for the description to add. Per guidelines, 0 params warrants a baseline of 4 since the description has no parameter documentation burden.

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 it lists active sessions with a specific verb and resource. However, it doesn't clarify what 'active' means versus other possible session states or distinguish it from siblings like get_state or dsl_reference. The purpose is clear but lacks distinguishing scope.

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 on when to use this tool versus alternatives. With siblings like create_session, get_state, and clear_session, there's no context explaining when listing sessions is appropriate or how it differs from checking a specific session's state.

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