get_conversation

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

With no annotations present, the description carries the full burden and does well: it discloses part-based pagination, the default budget (~60000 chars), the returned metadata fields, and that tool calls/results are stubbed by default to protect the budget. It does not cover error behavior for an invalid id or any access/permission constraints, which keeps it from a 5.

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?

Front-loads the core purpose, then the pagination contract, then the tool-IO caveat. Dense but every sentence conveys behavior an agent needs; the trailing tool-IO sentence partially duplicates the schema's include_tool_io description, costing a point.

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?

There is no output schema, so the description must describe return shape — and it does, naming total_messages, total_chars, returned {start, end (exclusive)} and next_start, plus truncation of oversized single messages. An agent has everything needed to page through a conversation to completion.

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%, so baseline is 3; the description earns above that by explaining the continuation protocol that binds `start` to `next_start` and by giving the rationale for `include_tool_io` (tool payloads are enormous and blow the part budget). It still defers the actual bounds and clamping to 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?

States a specific verb and resource ('Retrieve a specific conversation by ID with its messages'), which cleanly separates it from list_recent_conversations and search_conversations that operate without an ID. It does not explicitly name a sibling to contrast with, so it stops short of a 5.

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?

Gives explicit operational guidance for the common multi-call case: when next_start is not null, call again with the same id and start=next_start until null. That is clear context for correct invocation, though it offers no routing advice about using search_conversations or list_recent_conversations to discover an id first.

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