Get conversation

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

Annotations declare readOnlyHint: true, covering safety. The description adds value by specifying exactly what is loaded (messages, lineage, decisions, transcript), which is beyond the annotation. It does not disclose potential performance or size implications, but the read-only nature is already disclosed.

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?

A single, well-structured sentence that front-loads the core action ('Loads a stored conversation') and efficiently lists the contents. No redundant or unnecessary information, every word earns its place.

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?

For a simple get-by-id tool with no output schema, the description lists the return contents (messages, lineage, decisions, transcript), which is adequate. It does not mention error cases (e.g., not found) but given the read-only annotation and simplicity, this is acceptable.

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 0%, and the description does not mention the 'id' parameter or its role as the conversation identifier. While the parameter is inferable from its name and format, the description fails to compensate for the lack of schema documentation, leaving the agent to guess its meaning.

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 verb 'Loads' with the resource 'stored conversation' and lists the specific contents (messages, lineage, decisions, Markdown transcript). This distinguishes it from siblings like list_conversations (listing only) and search_conversations (searching), making the tool's purpose unambiguous.

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 for retrieving a single conversation's full content but does not explicitly state when to prefer this over siblings like list_conversations or search_conversations. No exclusions or alternative conditions are provided, leaving the agent to infer context.

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