session.list

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

With no annotations, the description carries the behavioral burden. It usefully discloses that results are concise metadata and that full entries are reachable via resource URI. However, it does not disclose default limit, pagination behavior, filter semantics, or explicit side-effect-free guarantees beyond the implied read-only nature of 'List'.

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, front-loaded sentences: the purpose comes first and the full-entry resolution path second. There is no filler, repetition, or unnecessary detail.

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 tool with six optional parameters and no annotations, the description is too sparse. It omits filter semantics, default behavior, and any guidance about combining or leaving filters empty. The output schema helps document return values, but the missing parameter context and usage caveats leave an agent guessing.

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?

All six parameters are optional and have no schema descriptions, so the description must compensate for 0% schema coverage. It does not mention any parameter or explain that user_id, tenant_id, etc. are filtering scopes or that limit controls page size. The description adds no meaning beyond the parameter names.

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 an explicit verb ('List') and identifies the resource ('session') with a scope qualifier ('concise session metadata'). By stating that full entries are obtained separately through the resource URI, it clearly distinguishes listing from full-content access and from the sibling write tool session.write.

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?

It implicitly guides the agent to use this tool for metadata browsing rather than full-content retrieval, pointing to the resource URI for full entries. It does not explicitly name sibling tools or state when not to use filters, but the core when-to-use decision is conveyed.

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