Get Conversation Messages

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description does not need to cover safety. It adds some context about return content ('SMS, email, and other message types') but does not disclose pagination, ordering, or default limit behavior. Given the strong annotations, this is adequate but not exceptional.

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 concise and front-loaded with the verb and resource. Two sentences provide essential information without unnecessary detail. Every word contributes value, and the structure is immediately scannable.

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?

Although the tool is simple and annotations cover safety, the description lacks some contextual details that would improve completeness. Without an output schema, it only vaguely hints at return content ('SMS, email, and other message types') and does not mention pagination, default limit, or that conversationId is required (though schema covers that). For a basic getter with strong annotations, this is minimally complete but leaves room for improvement.

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 67% (conversationId and type are described; limit is not). The description does not add any new parameter semantics beyond what the schema already provides—'SMS, email, and other message types' essentially reiterates the schema's type filter description. The limit parameter remains undocumented in both schema and description, and the description does not clarify how parameters interact.

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 tool's function: retrieving messages from a conversation thread. It uses a specific verb ('Get') and resource ('messages in a conversation thread'), and distinguishes itself from sibling tools like ghl_get_conversation (which likely retrieves conversation metadata) and ghl_send_message (which sends 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 when to use the tool (when you need messages in a conversation) but does not provide explicit guidance on when to use it instead of alternatives like ghl_get_conversation or ghl_search_conversations. No exclusions or alternative tool names are mentioned, so the usage context is only implied.

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