list-sessions

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

With no annotations, the description carries the full burden. It indicates a read-only listing operation via 'list' and adds context about 'recent' sessions and account scope, but does not disclose return format, pagination behavior beyond schema, or any potential side effects. This is adequate for a simple list tool but minimal.

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 sentence that front-loads the verb and resource, followed by the optional filters. There is no filler or redundancy, making it maximally concise and well-structured.

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 action and filters, and the schema documents all parameters. However, with no output schema, it does not describe the return shape or ordering behavior beyond 'recent'. This is sufficient for a simple list but leaves some gaps.

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 input schema has 100% description coverage for all four parameters (limit, offset, status, packageId). The description adds minimal semantic value by summarizing the filters for package and status, but does not explain limit/offset beyond what the schema already provides. Baseline 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 clearly states the tool lists sessions on the account, with a specific verb ('List') and resource ('sessions'). It differentiates from siblings like get-session (singular retrieval) and list-packages (different resource) by focusing on session listing.

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 usage for listing sessions with optional filters, but does not explicitly mention when to prefer this over get-session or other siblings. No exclusions or alternative guidance is provided, so usage context is only implied.

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