sessions_list

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

With no annotations, the description carries the behavioral disclosure burden. It conveys that the tool returns recent sessions and implies a read-only listing, but it does not specify ordering, time window, pagination behavior, or whether any side effects occur. This is adequate for a simple list tool but not richly transparent.

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 a single, front-loaded sentence with no filler. The purpose clause adds value rather than redundancy, making it both concise and structured effectively.

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 one optional parameter and an output schema, the description is nearly complete. It states the resource, purpose, and recency constraint. Minor gaps remain around what 'recent' means and how limit behaves, but these are not critical given the simple interface and available output schema.

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 single parameter, limit, has no schema description and the tool description does not mention it at all. The parameter name and default value are self-explanatory, but the description adds no meaning beyond the schema, and schema coverage is 0%.

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'), a clear resource ('recent sessions'), and states the intended purpose ('so you can resume or inspect one'). It clearly distinguishes this tool from sibling list tools like cron_list and skills_list by naming the resource and user goal.

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 phrase 'so you can resume or inspect one' provides clear context for when to use the tool. However, it does not explicitly mention alternatives or when not to use it, though the resource and purpose are sufficient to infer typical usage.

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