get_conversation_messages

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

With no annotations provided, the description carries the full burden. It clearly labels the operation as 'Read', implying a non-mutating call, and it discloses the limit behavior. However, it creates a mild ambiguity by claiming 'full message history' while the limit parameter caps retrieval to recent messages, and it omits ordering, matching semantics, or error behavior.

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 compact and front-loaded: one clear purpose sentence followed by a minimal, well-structured args list. Every sentence adds value, and there is no redundant restating of schema fields.

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 low parameter count and the existence of an output schema, the description covers the essential invocation details: purpose, key parameter semantics, and limits. It is slightly incomplete in resolving the 'full history' vs 'recent messages' tension and does not mention pagination, but overall an agent has enough to call the tool correctly.

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 and does compensate. It explains recipient_name as 'Name or keyword matching the conversation partner', adding meaningful semantics beyond the schema title, and gives limit an explicit maximum (30) not present in the schema, plus its default.

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 uses a specific verb ('Read') and names a precise resource ('full message history and replies for a specific conversation in your inbox'), making the tool's function immediately clear. It is naturally distinguishable from siblings like list_conversations or send_message without needing to open schemas.

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 phrase 'for a specific conversation' and 'in your inbox' gives clear context for when the tool applies, and the sibling list confirms it is the message-retrieval counterpart to list_conversations. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of a 5.

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