get_chat_messages

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

As no annotations are provided, the description carries full burden. It describes return format with sender info and timestamps, and mentions pagination. However, it does not explicitly state that the operation is read-only or disclose any side effects, which would help an agent understand safety.

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 brief and well-structured with Args and Returns sections. Every sentence is necessary and front-loaded with the purpose. No redundant information.

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 simplicity of the tool (3 parameters, no output schema, no annotations), the description covers essential aspects: required chat_id, pagination with limit and cursor, return format. It lacks details on error handling or rate limits, but is reasonably complete for a read operation.

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?

With 0% schema description coverage, the description adds significant meaning: explains chat_id as from list_chats, limit as max per page with default 50, and cursor as pagination from previous response. This compensates for the lack of schema param descriptions.

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 'Get messages from a specific chat conversation,' specifying the verb and resource. It distinguishes from sibling tools like list_chats, send_message, start_chat by focusing on retrieval of messages.

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 implies that chat_id comes from list_chats and explains pagination parameters, but does not explicitly state when to use this tool versus alternatives like list_chats (which lists chats themselves) or send_message (which sends messages). No exclusion criteria or context for when not to use it.

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