get_chat_messages

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

No annotations are supplied, so the description carries the burden and does disclose meaningful behavior: oldest-first ordering, paging semantics via before_id, and Claude-side rendering as an inline card. It stops short of stating read-only safety, rate limits, or default truncation consequences.

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?

Front-loaded with the core action, then the rendering caveat, then args. Every sentence is useful, though the Claude-specific rendering note is slightly verbose for an agent-facing definition.

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?

With an output schema present, the description needn't explain return values, and params are all covered. For a scoped, read-only read tool this is close to complete; the only gaps are the missing explicit read-only/rate-limit framing.

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, and it does: chat_id is tied to list_chats, limit is defined as max messages with default 50, and before_id is explained as "older than this message id, to page back through history." It could go further on boundary behavior, but all three params are meaningfully covered.

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+resource ("Read messages") scoped to "one conversation," and adds the ordering guarantee (oldest-first). It implicitly separates itself from conversation-wide search, though it does not name search_messages or get_message explicitly.

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?

Usage is implied rather than stated: it tells the agent to page back with before_id and points at list_chats for the chat_id source, plus a rendering hint. There is no explicit when-to-use-this-vs-search_messages/get_message guidance or when-not condition.

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