sassy_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. 'List' clearly implies a read-only, non-destructive operation, and the 'active' qualifier tells the agent which sessions are included. However, it omits any statements about side effects (e.g., that no sessions are modified) or potential authentication/context requirements, though for a listing tool these are largely implicit.

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, direct sentence of six words. It front-loads the main action and resource without any superfluous content, achieving maximum conciseness while remaining clear.

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 the tool's simplicity (no params) and the presence of an output schema, the description adequately covers what the tool does. It could be improved by adding a hint about how it relates to sibling session tools (e.g., 'use before sassy_session_read'), but it does not feel incomplete for its scope.

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 input schema is empty, so there is nothing to document. Per the baseline rule for 0 parameters, this scores 4; the description correctly offers no parameter details because none exist.

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 'List all active terminal sessions' uses a specific verb ('list') and a clearly defined resource ('active terminal sessions'). It distinguishes from sibling tools like sassy_session_start, sassy_session_read, and sassy_session_stop, which all involve other session operations.

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 gives no guidance on when to use this tool versus alternatives. It does not mention that one might list sessions before starting, reading, or stopping them, nor does it contrast with the session-management siblings. The agent must infer usage solely from the tool name.

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