List Sessions

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

With no annotations, the description must carry the behavioral disclosure burden. 'List' reasonably implies a read-only, non-mutating operation, and 'indexed sessions' hints that results come from an index, but the description does not explicitly state side-effect safety, freshness semantics, or any auth requirements.

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 sentences with no filler. The core action and output fields are front-loaded, and the usage guidance is included in the second sentence.

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 low-complexity list tool with full parameter schema coverage and an output schema, the description is nearly complete. The main gap is that 'indexed' is not elaborated, which could matter given the refresh_index sibling and potential index freshness concerns.

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?

Schema description coverage is 100%, and each parameter already has a meaningful description with defaults and allowed values. The tool description adds no parameter-level detail beyond context, so the baseline of 3 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?

The description uses a specific verb and resource ('List indexed sessions') and enumerates the returned fields (id, title, project, last activity). It also differentiates the tool from its primary sibling by framing it as a picker before locate_and_load_session.

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 clear workflow context: use it to pick a session before calling locate_and_load_session. It names the relevant sibling alternative, though it does not explicitly address when not to use it relative to save_active_session or refresh_index.

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