list_sessions

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

With no annotations, the description must disclose behavior. It mentions filters but fails to clarify the significant default behavior: when 'user' is omitted, it uses the current user, which may conflict with the phrase 'all saved sessions'. It also does not state whether the operation is read-only or if any side effects occur. This is a substantial gap.

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 entire description is two short sentences and immediately front-loads the core purpose. No unnecessary words 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 main action but leaves out key contextual details like the default user filter scope, the meaning of 'saved sessions', and any pagination or ordering behavior. Given no output schema and no annotations, this is insufficient.

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 schema fully describes both parameters with descriptions, and the tool description only restates the filtering capability. No additional meaning or format details are provided beyond the schema, so the baseline score 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 ('List') and resource ('saved sessions'), clearly distinguishing it from session lifecycle tools like save_session, start_session, or delete_session. The optional filter by project/user is also stated, making the tool's scope obvious.

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 a read-only listing use case, which is clear from the name and sibling context. However, it does not explicitly state when to use this instead of other session tools or mention exclusions, so it falls short of 'explicit when/when-not' guidance. Clear context but no alternatives named.

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