read_conversation

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

Description only states it reads and gets full message history, implying a read-only operation. However, no annotations are provided, and the description does not disclose any behavioral traits such as pagination, rate limits, permissions, or side effects. With no annotations, the description should provide more transparency about limitations or performance.

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 extremely concise, consisting of two short sentences that front-load the main purpose. Every sentence adds value without superfluous details.

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 tool's simplicity (3 parameters, no nested objects, output schema exists), the description is mostly complete. However, it lacks context about how to obtain prerequisite information like conversation_id from list_inbox, and does not mention any integration with sibling tools. Overall adequate but not exhaustive.

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 100% for all three parameters. The description does not add any extra meaning beyond what the schema already provides. Baseline 3 is appropriate as the schema does the heavy lifting.

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 the tool reads all messages in a conversation and provides full message history of a DM or comment thread. It uses specific verbs and resource, distinguishing from sibling tools like list_inbox (which lists conversations) and reply_to_message (which sends messages).

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?

The description implies usage when you want to read messages, but does not explicitly state when to use it versus alternatives. It could mention that conversation_id should come from list_inbox, or that this is not for sending messages. Lack of explicit guidelines reduces clarity for selecting the correct tool.

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