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

With no annotations, the description carries the full burden and does well: it discloses the authentication requirement (MCP_API_KEY via x-api-key or Bearer), the exact failure mode (error_code operator_key_required), and that the chat agent and local STDIO server are excluded. It omits ordering of results and pagination behavior, which an agent would want for a list tool.

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?

Three tight sentences: purpose and return fields first, usage trigger second, access constraint third. No filler, and the most decision-relevant information is front-loaded.

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?

No output schema exists, and the description compensates by listing the returned fields. Auth and error behavior are covered. The main gap is result ordering and whether more than 100 conversations require paging, minor for a single-parameter list tool.

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 coverage is 100% and the only parameter (limit, default 20, max 100) is fully documented in the schema. The description adds no parameter-level detail such as ordering or cursor behavior, so baseline 3 applies.

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?

States a specific verb and resource (list stored chat conversation sessions) and enumerates exactly what each entry contains: ID, last-updated timestamp, turn count, and a preview of the most recent user message. This distinguishes it clearly from destructive siblings like delete_conversation and from analytics siblings like analyze_session_usage.

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?

Explicitly says when to use it: 'when the user asks to see their past conversations or chat history.' The operator-only constraint is a strong gating condition, though no alternative tool is named for the non-operator case, leaving the fallback route implicit.

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