List Sessions (v3)

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

Annotations already declare read-only, idempotent, and open-world hints, so the safety profile is covered. The description adds minimal behavioral context: it mentions filtering by 'agent or source,' which aligns with parameters, but does not explain return behavior, ordering, or pagination (beyond schema hints). It does not contradict annotations.

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 fluff. Every word earns its place, efficiently conveying the core purpose and optional filters.

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?

Given the rich sibling context (many session-related tools) and lack of an output schema, the description is too terse. It fails to explain what a 'v3 session' is, what 'source' refers to, or what the response format contains, leaving significant ambiguity for an agent attempting to invoke the tool correctly.

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 100%, so the schema fully documents all four parameters (limit, offset, source, agent_id). The description adds no new semantic detail beyond what the schema already provides, so the baseline score of 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's function: 'List v3 sessions, optionally filtered by agent or source.' This provides a specific verb ('List'), a clear resource ('v3 sessions'), and unique differentiators (optional filters), distinguishing it from sibling tools like session3_list_messages or session3_get.

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 (list v3 sessions with filters) but does not provide explicit when-to-use guidance relative to sibling tools, nor does it state exclusions or alternatives. It is not misleading, but it lacks direct comparative context.

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