get_conversation

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so safety is covered. The description adds nothing beyond that: it doesn't say whether 'details' include messages, notes, or metadata, nor under what conditions the call fails (unknown convoId, wrong agentId, cross-workspace). For a lookup whose main risk is a wasted/incorrect call, that is a real gap.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity tips into under-specification rather than pure concision.

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?

There is no output schema, so the description is the only place an agent could learn what a 'detail' payload contains and how it differs from a list entry. It supplies none of that, leaving the tool under-described for a no-output-schema read.

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 two fully described required parameters, so the schema carries parameter meaning. The description adds no semantics of its own, such as whether agentId must own convoId or whether the IDs are global — baseline 3 is correct.

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?

Clear specific verb (get) and resource (a single conversation), and 'single' distinguishes it from list_conversations reasonably well. However, it doesn't differentiate itself from query_conversations or get_conversations_bulk, which plausibly return similar conversation records.

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 when-to-use statement and no alternatives named, despite four sibling conversation-read tools in the list. The agent must infer that this is the by-ID lookup versus the list/query/bulk variants.

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