list_conversation_messages

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

With no annotations, the description must disclose behavioral traits. It adds pagination behavior and ordering (oldest first), but does not mention auth requirements (api_token parameter), error behavior, or whether it is read-only (though 'page through' implies a read operation). This is a gap but not a contradiction.

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 sentence that is directly to the point, with no filler. It front-loads the primary purpose (pagination) and adds a useful ordering detail without wasting words.

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?

The tool is relatively simple and an output schema exists, so return values may be documented there. However, the lack of parameter explanations and any mention of cursor/limit usage leaves the agent partially in the dark about how to perform pagination beyond the phrase 'Page through'.

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. It does not mention any parameter names or semantics—conversation_id, limit, cursor, and api_token are all undocumented in the description. The agent gets no help understanding how to use these parameters.

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 uses specific verb 'Page through' plus resource 'a conversation's sent messages' and ordering 'oldest first'. This clearly distinguishes it from siblings like list_conversations (lists conversations) and get_message (fetches a single message).

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 makes it clear this is for paginating through sent messages of a specific conversation, which implies when to use it. However, it does not explicitly mention alternatives or when not to use it, such as using list_conversation_comments for comments or 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.