session_list_tool

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

No annotations are provided, so the description carries the behavioral transparency burden. The verb 'List' clearly indicates a read-only operation, and 'who's on this box right now' signals a live/snapshot behavior. It also discloses the return shape ('List of sessions with count'), which is sufficient for a simple listing tool.

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 two short, front-loaded parts: a plain-language purpose and a compact return contract. Every line contributes useful information without redundancy, making it easy for the agent to parse quickly.

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 tool with an output schema already present, the description is complete enough. It states what the tool listsainer, conveys 'right now' current-state semantics, and explicitly mentions the count in the return value. No additional behavioral or usage information is needed for correct invocation.

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 the description cannot add parameter-level meaning. Per the baseline for 0-parameter tools, this is appropriately complete; there is nothing about parameters the agent needs to know.

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 and resource: 'List logged-in sessions' and clarifies scope with 'who's on this box right now.' This clearly distinguishes it from the sibling unit and system tools, which target services, host info, or system status.

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 provides clear context for when to use the tool: when the agent needs to know currently logged-in sessions on the host. It does not explicitly name alternatives or exclusions, but given the sibling list, no competing session-listing tool exists, so the usage context is unambiguous.

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