get_chat_messages

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

With no annotations, the description carries the behavioral disclosure burden. It clearly states this is a read operation, specifies oldest-first ordering, and explains how limit and before_id control paging. It does not discuss auth or side effects, but 'Read messages' strongly implies non-mutating 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, front-loaded with the core purpose, and each parameter line adds semantic value rather than repeating schema metadata. There is no filler or redundancy.

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 modest complexity and the presence of an output schema, the description covers the essential usage: what it reads, ordering, limits, and paging. It could add a note about when to prefer search_messages or get_message, but the core calling context is complete.

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%, and the description fully compensates by explaining each parameter in plain language. It also adds critical provenance for chat_id ('Conversation id from list_chats') and explains before_id's pagination role, which the schema's type/title fields do not convey.

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 opens with a specific verb and resource: 'Read messages from one conversation', which clearly distinguishes it from sibling tools like get_message (single message) or search_messages. The scope 'one conversation' plus ordering ('oldest-first') makes the tool's purpose unambiguous.

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 opening states when to use it — retrieving full history for a single chat — and the before_id parameter provides paging context. It does not explicitly name alternatives or say 'use get_message for a single message', so it lacks explicit exclusions, but the usage context is clear.

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