elster_session_list

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

No annotations provided, so description must be transparent. It states sessions are listed with status, but does not disclose if the tool is read-only, requires authentication, or has any side effects. Adequate for a simple list, but lacks depth.

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?

Single sentence, efficient, front-loads purpose and scope. Could be slightly more informative about what 'status' entails, but no waste.

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 zero parameters and no output schema, the description is mostly complete for a simple list tool. It mentions session types and status, though it could clarify the meaning of status or mention any limits. Still adequate.

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?

No parameters, schema coverage 100% => baseline 4. Description does not need to add param info, so score is appropriate.

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 uses specific verb 'Lists' and resource 'currently tracked sessions' with enumerated session types and status, making purpose immediately clear and distinguishing from sibling tools like elster_session_status which likely focus on single sessions.

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 explicit guidance on when to use this tool vs alternatives. The description implies it's for an overview, but does not state exclusions or conditions such as 'use this to get a list before canceling a session'.

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