Get conversation messages

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

Annotations already declare readOnlyHint=true, so 'Read-only' adds nothing new; the ordering guarantee ('oldest first') is genuine added behavioral context. It does not describe pagination behavior, result volume, or the limits of the openWorld data source.

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?

Two short sentences that are entirely front-loaded: the action first, then the sourcing hint, then the safety/ordering note. No filler.

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 read tool with an output schema absent, the definition covers identity, sourcing, and ordering, and the schema covers the page-size parameter. Missing only a note on how paging/offset works in practice, which is a minor gap.

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 coverage is 67%: limit and conversation_id are documented inline, offset is not. The description adds only the provenance of conversation_id and says nothing about paging, so it neither compensates for the gap nor overrides the schema.

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 and resource ('Return the messages of one conversation'), and the parenthetical identifies the ID's provenance, distinguishing it from siblings like list_messages and get_message. An agent knows exactly what this returns without opening the schema.

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?

Explicitly tells the agent where the required conversation_id comes from (list_conversations or a message's conversationId), which is real routing guidance. It does not, however, state when not to use it or contrast it with get_message for a single message.

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