list_sessions

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description contributes no additional behavioral context such as default date ranges, sorting, timezone semantics, pagination behavior, or data scope.

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 extremely short but under-specified. 'List Sessions' is concise in length but not in value: it contains no information beyond the tool name/title and does not earn its place as an explanatory definition.

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?

With a complete output schema, rich annotations, and self-documenting parameters, the tool is minimally invocable from structured data alone. However, the description leaves unstated what counts as a 'session' and how this relates to the singular get_session tool, so it is only barely adequate.

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 documents all seven parameters with descriptions, giving 100% schema description coverage, so the baseline is 3. The description itself adds no parameter-level meaning beyond what the schema already provides.

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 'List Sessions' is essentially a tautology of the tool name and title. It identifies the verb and resource but provides no scope, meaning of 'session', or differentiation from sibling tools such as get_session or list_session_feedback.

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?

There is no guidance on when to use this tool instead of alternatives. No exclusions, no mention of get_session for single-session lookup, and no indication of whether this is the canonical list endpoint among many sibling list_* tools.

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