get_conversation

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond that, with no mention of error behavior for unknown ids, permission requirements, or what 'detail' comprises.

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?

One front-loaded sentence with zero padding, exactly matched to the tool's scope. It is terse to the point of being thin, but nothing in it is wasted.

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?

The tool is simple (one required parameter, full schema coverage, annotations present), so little is strictly required. But with no output schema, the description gives no indication of what the 'detail' response contains or how large it may be, leaving an agent to call blind on the return side.

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?

There is a single parameter with 100% schema description coverage, so the baseline is 3. The phrase 'by id' is consistent with conversationId but adds no format, validation, or sourcing guidance (e.g., where to obtain the id) beyond what the schema already says.

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?

States a specific verb (get) and resource (conversation detail) scoped by id, which is clear enough to distinguish from mutations like update_conversation_status. However, it never distinguishes itself from sibling reads such as list_conversations, search_conversations, or list_messages, despite those being the closest alternatives.

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 on when to use this versus search_conversations or list_conversations, and no note that it requires a known conversationId (so it cannot be used for discovery). Usage is only implied by the phrase 'by id'.

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