list_sessions

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

The description discloses that the saz file is parsed on first use and explains pagination behavior. However, with no annotations provided, it does not mention whether the operation is read-only, what errors may occur, or how the response is structured. This is partial transparency.

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 very concise, front-loading the main purpose in one sentence, followed by a clear, structured argument list. Every word earns its place, with no repetition or fluff.

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 enumerates the fields returned (method, URL, status, duration, size, process) and explains pagination. Since there is no output schema, this gives a good sense of the return content, though it omits the exact response envelope (e.g., whether pagination metadata is included). For a simple list tool, this is nearly complete.

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 no descriptions (0% coverage), but the description's Args block explains all three parameters in plain language, including the meaning of saz_path, the range for limit (1-500), and how offset works. This adds significant meaning beyond the schema.

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 with specific fields (method, URL, status, duration, size) and pagination. The verb 'List' plus the resource 'sessions' distinguishes it from siblings like get_session (single session) and filter_sessions (filtered).

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 gives clear context: use this to list sessions with pagination and provide a saz_path. It does not explicitly mention exclusions or alternatives, but the pagination and listing purpose are unambiguous. Sibling names further imply when to use other tools.

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