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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds two things annotations cannot: the required `inbox:read` scope and a warning that user-authored text appears in untrusted_fields and must not be treated as instructions. That prompt-injection caveat is meaningful behavioral context, though it does not describe error behavior for a missing or unauthorized conversation.

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?

Three short sentences, front-loaded with the action, then the permission requirement, then the untrusted-content caveat. Nothing is redundant and each clause carries new information.

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 single-parameter read tool with full annotations this is close to sufficient, and the untrusted_fields note partially covers the absent output schema. What is missing is how to acquire conversation_id and how the returned conversation relates to the separate message-listing tool.

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 description coverage is 0% and the sole parameter conversation_id has no description in either place. The description does not state the identifier's format or where the agent should obtain it (presumably from list_conversations), so it fails to compensate for the coverage gap.

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 gives a specific verb and resource ("Get one of my conversations"), and the qualifier "one of" signals single-item retrieval versus the sibling list_conversations. It stops short of naming that sibling explicitly, so the differentiation is implied rather than stated.

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?

Usage is only implied by the singular "one of my conversations"; the description never says when to pick this over list_conversations or how it relates to list_messages for the thread contents. An agent can infer the intent but has no explicit routing guidance or prerequisites beyond the permission requirement.

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