Get Conversation

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

Annotations already indicate readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds the required scope (conversations.readonly) and the GET endpoint, which provides useful context beyond annotations. No contradictions; the description aligns with the read-only nature.

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 short but begins with a redundant repetition of the title ('Get Conversation') before stating the actual purpose. It could be more concise and front-loaded by removing the redundant prefix. No excessive length, but structure could be improved.

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 one parameter, no output schema, and a rich annotation set, the description provides enough context: it specifies the endpoint, scopes, and purpose. It doesn't need to explain return values or error handling for a tool this straightforward, so it is adequately complete.

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?

The schema fully describes the only parameter (conversationId as string, 100% coverage). The description offers no additional meaning about the parameter, so the baseline of 3 applies. Not adding extra detail is acceptable given the schema's completeness.

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 tool retrieves conversation details by ID, with the endpoint and scopes. It distinguishes itself from search tools by relying on the ID, though it doesn't explicitly contrast with siblings like conversations_search_conversation. The redundancy of repeating 'Get Conversation' at the start slightly detracts from precision.

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 guidance is provided on when to use this tool versus alternatives such as conversations_search_conversation or conversations_get_messages. The intended use case (having a conversationId) is implied but never stated, so an agent might not know when to prefer this over a search.

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