Get conversation

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

The description says 'Get details', which aligns with the readOnlyHint annotation, but it adds no behavioral context beyond what annotations already provide. With readOnlyHint=true and openWorldHint=true, the description should contribute extra information (e.g., what 'details' includes, any restrictions) but does not.

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 sentence and not verbose, but it sacrifices informativeness for brevity. It is minimally adequate but does not earn its place by adding value beyond the tool name.

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?

Given the low complexity (1 parameter, no output schema) and many sibling tools, the description lacks completeness. It does not explain return format, difference from siblings, or any behavioral nuances, leaving the agent under-informed for correct invocation.

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 input schema has one parameter (conversationId) with 0% coverage in the description. While the parameter name is self-explanatory, the low coverage requires the description to clarify its meaning or usage, which it fails to do. The description does not mention the parameter at all.

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 'Get details of a specific conversation', using a specific verb and resource. It distinguishes from the sibling 'get_conversations' (plural) by implying singular retrieval, but it does not elaborate on what 'details' includes, slightly reducing clarity.

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 guidance is provided. The description does not indicate when to use this tool over alternatives like 'get_messages' or 'get_conversations', leaving the agent to infer based on the tool name alone.

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