list_claude_sessions

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

No annotations are provided, so the description carries full burden. It explains the behavior of the two parameters (filtering by project, limiting results) but does not disclose other behavioral traits such as read-only nature, sorting order, pagination details beyond limit, or any side effects. The description is adequate but lacks broader context.

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 short, clear, and uses a structured bullet format for arguments. No unnecessary words, and the key information is front-loaded. Every sentence earns its place.

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 simple list tool with 2 optional parameters and an output schema, the description covers the essential parameter behavior and filtering logic. However, it could mention that the result is a list of sessions (though output schema likely handles that) and any default ordering. Overall, it is mostly complete given the tool's simplicity and available 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?

Schema description coverage is 0%, but the description fully explains both parameters: project_slug (use from list_claude_projects, leave empty for all) and limit (max number, default 20). It adds critical meaning that the schema alone does not provide, making parameter usage clear.

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 'List Claude Code sessions' with optional filtering by project. It distinguishes itself from sibling tools like get_claude_session (single session) and search_claude_sessions (search) by being a general listing tool. The purpose is specific and unambiguous.

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 explains how to use the project_slug parameter (from list_claude_projects) and when to leave it empty, but does not explicitly state when to use this tool over siblings like search_claude_sessions or get_claude_session. Usage context is implied but not compared with alternatives.

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