get_conversation

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

With no annotations, the description carries the full burden and adds useful behavioral details: the read is from the 'authoritative JSON store', and the response content is capped to protect model context. It could mention error behavior when the ID is not found, but the disclosed behaviors go beyond a bare getter.

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 two lean sentences with no filler. The primary purpose is front-loaded, and the second sentence adds a meaningful operational constraint about content truncation.

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 retrieval tool with an output schema, the description covers purpose, source, and the one tunable behavior (content cap). It is adequate for an agent to select and call the tool, though it leaves not-found/error behavior unspecified.

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 0%, so the description must compensate. It does: conversation_id is contextualized as an ID returned from a search tool, and max_chars is explained as the content cap that can be increased when needed. It does not specify units or range, but the default in the schema covers some of that gap.

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 uses a specific verb ('Retrieve') and a clear resource ('a stored conversation by an ID'), which immediately identifies it as a point-lookup tool. The mention that the ID comes from a search tool further separates it from the search-family siblings.

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 provides clear usage context: call this after obtaining a conversation ID from a search tool. It does not explicitly name sibling alternatives or state when not to use it, but the intended workflow is evident.

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