Get conversation messages

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

The annotations already provide readOnlyHint and openWorldHint. The description adds the 'newest first' ordering behavior, which is a useful trait beyond the annotations. It does not describe pagination or response format, but the annotation coverage reduces the burden.

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?

Two sentences with no redundancy. The core action and ordering are front-loaded, and the pointer to a sibling tool is concise and useful.

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 description covers the required input (conversationId) and tells where to get it, and annotations cover read-only safety. It does not mention the return structure, which would be helpful given no output schema, but overall it is largely adequate for a simple read tool.

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 only indirectly references conversationId by telling how to find it. It does not explain the limit parameter's purpose or constraints, leaving a semantic gap for the agent.

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 action ('Fetch') and resource ('messages within a conversation thread'), and adds 'newest first' as a specific behavior. It also differentiates from siblings by pointing to ghl_search_conversations to find a conversationId, making its purpose distinct.

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?

It explicitly directs the agent to use ghl_search_conversations to find a conversationId, which is a clear prerequisite and alternative pointer. However, it does not explicitly mention when not to use this tool (e.g., when sending a message), so it lacks full exclusion guidance.

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