read_conversation

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the output is the 'most recent messages of a conversation (newest last)' which conveys ordering, but doesn't disclose whether this is a read-only operation, whether account scoping affects results, pagination behavior beyond the limit, or what happens with invalid conversation IDs. Given zero annotations, this is a significant disclosure 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?

The description is a single concise sentence that packs in the key details: 'up to limit most recent messages', conversation scope, and ordering. It's efficient with no filler. However, it front-loads reasonably well and earns its single sentence.

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?

An output schema exists which reduces the need to explain return values, but the tool deals with a conversation context involving 3 params where 1 (account) is entirely unexplained, no annotations exist, and sibling overlap (recent_messages) creates ambiguity. The single-sentence description is inadequate for an agent to correctly select and invoke this tool among the 7 siblings—particularly around the account parameter and differentiation from recent_messages.

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%, so the description must compensate for all three parameters (conversation_id, limit, account). It explains 'limit' explicitly and conversation_id implicitly through 'of a conversation', but 'account' is entirely undocumented—the agent has no idea whether it filters, scopes, or authenticates the read. There's no mention of the conversation_id format or how account and conversation_id interact.

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 a specific verb (return/read) and resource (conversation messages), with 'newest last' ordering, which conveys the operation and result ordering. However, it doesn't explicitly distinguish from sibling tool 'recent_messages' or 'list_conversations'—the agent must infer that 'read_conversation' returns messages within a single conversation whereas 'list_conversations' lists conversation metadata.

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?

There's no guidance on when to use this tool vs. alternatives like search_messages or recent_messages. The description mentions 'limit most recent messages' which partially overlaps with recent_messages, creating possible confusion. No when-not-to-use or alternative references are provided.

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