list_sessions

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

No annotations were provided, so the description carries the full burden. It discloses the auto-login side effect, which is useful, but it does not mention pagination, rate limits, or the absence of filtering. For a read-only list tool, this is a moderate disclosure.

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?

Two short, purposeful sentences. The primary action (list sessions) is front-loaded, followed by the API path and a note about auto-login. No filler or repetition.

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?

The description covers the core operation and the auto-login behavior, but with no output schema and no mention of response format or any query capabilities, an agent might lack enough detail to fully anticipate the result. For a simple list endpoint this is borderline sufficient, but it leaves room for clarification.

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 schema is empty, so the description has nothing to add. Per the calibration, a baseline of 4 applies when no parameters exist; the description correctly avoids inventing parameter info.

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?

Verb 'List' plus resource 'agent conversation sessions' and ordering 'newest first' clearly identifies the operation. Naming the exact endpoint (GET /api/v1/sessions) and the auto-login behavior makes it distinguishable from siblings like get_session or list_prompts.

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 implies this is for listing all sessions, but it does not explicitly contrast with get_session (for a single session) or state conditions for when to prefer this over list_prompts. No exclusions or prerequisites are given, so usage context is only implicit.

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