conversations_get_conversation

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety and idempotency. However, the description adds no behavioral context beyond that—it doesn't mention return format, whether the full conversation object is returned, or any constraints. Given the annotation coverage, the bar is lower, but the description still fails to provide meaningful behavioral details.

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 a single phrase, 'Get Conversation', which is extremely sparse. While it is concise, it is under-specified and lacks any structure or useful information. The string is essentially the tool name with no added value, making it more of a placeholder than a structured description.

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 get-by-ID tool with a clear sibling (conversations_search_conversation) and no output schema, the description should clarify what a conversation is, what is returned, and when to use this as opposed to searching. The current description provides none of this context, leaving the agent to infer everything from the parameter name and tool name.

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% for the single parameter conversationId, with a clear schema description 'Conversation ID as string'. The tool description adds nothing beyond the schema, which is acceptable per the baseline for high coverage, but it also does not contribute any additional semantic clarity.

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 'Get Conversation' simply restates the tool name without adding any specificity. It doesn't indicate what a conversation is, what data is returned, or how it differs from sibling tools like conversations_search_conversation or conversations_get_messages. This is nearly a tautology.

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?

No usage guidelines are provided. The description offers no guidance on when to use this tool versus alternatives such as conversations_search_conversation or conversations_get_messages. An agent has no indication of prerequisites, use cases, or why to pick this over similar tools.

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