ensp_telnetListSessions

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

No annotations are provided, and the description only says 'List active eNSP Telnet sessions.' It does not clarify what 'active' means, whether the operation is read-only, if authentication is needed, or any limitations. For a listing operation, it implies no side effects, but this is not explicit.

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 sentence that conveys the core purpose without any extraneous words. It is front-loaded and efficient.

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 simple list tool with no parameters, the description gives the essential purpose. However, without an output schema or description of the return values (e.g., session IDs, state), the agent lacks full context on what information it will receive. Additional details about the output format would improve completeness.

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 no parameters, so the description need not explain parameter semantics. The baseline for zero parameters is 4, and the description does not mislead or add unnecessary information about parameters.

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?

Description clearly states 'List active eNSP Telnet sessions.' The verb 'List' and resource 'active sessions' are specific. It distinguishes from sibling tools like ensp_telnetConnect or ensp_telnetExecute by focusing on listing rather than connecting or executing commands.

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 vs alternatives. There is no mention of prerequisites, best practices, or context when listing sessions is appropriate (e.g., before connecting). The agent receives no help in deciding to use this tool.

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