Get Conversation

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

Describes what is returned (assignees, labels, metadata), which adds behavioral context beyond the schema. However, no annotations are provided, and the description does not mention read-only nature, permissions, or error states.

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?

Single sentence that is front-loaded with the core action and resource. No unnecessary words.

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 with one parameter and no output schema, the description adequately explains the purpose and return content. Could mention the format of the returned object, but not strictly necessary.

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% with a parameter description. The tool description adds no additional meaning beyond the schema's parameter description. Baseline score of 3 applies.

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?

Clearly states the verb 'Gets', the resource 'a single conversation by ID', and mentions the return content (assignees, labels, metadata). Differentiates from sibling tools like list_conversations and get_conversation_timeline.

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?

Implicitly indicates use when you need a specific conversation by ID, but no explicit guidance on when not to use or alternatives. Could benefit from contrasting with list_conversations or get_message.

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