conversations_get_messages

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

The description adds no behavioral context beyond the annotations. Annotations already state readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description does not mention pagination, ordering, or that it returns a list, despite the schema including limit and lastMessageId. This is a missed opportunity to enrich the agent's understanding.

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 front-loads the core purpose. No fluff, no repetition. It is appropriately sized for the tool's simplicity.

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?

Without an output schema and with no explanation of return structure or pagination workflow, the description leaves gaps. The agent must infer that it returns a list of messages and how to page through them using the provided parameters. Sibling tools increase ambiguity, and there is no guidance to disambiguate. This is incomplete for a read operation that supports filtering and pagination.

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%, so the schema already documents all parameters including the default limit and the purpose of lastMessageId. The description adds no extra parameter semantics; baseline of 3 applies because the schema carries the load, and the description does not clarify nuances like how to combine limit and lastMessageId for pagination.

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 action (get) and resource (messages) keyed by conversation id. It distinguishes from siblings like conversations_get_conversation and conversations_get_message by the plural 'messages' and the explicit 'by conversation id', though it does not explicitly contrast with the singular variant.

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 offers no guidance on when to use this tool versus alternatives such as conversations_get_message or conversations_search_conversation. It neither lists conditions for use nor mentions when not to use it, leaving selection to the agent's inference from the name and schema.

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