Get GHL Conversation

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

Annotations already indicate a safe, read-only, idempotent operation. The description adds 'with metadata,' hinting at the return payload, but does not detail response behavior (e.g., not-found handling). This is acceptable for such a simple getter, but not particularly rich.

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, front-loaded sentence with zero redundancy. Every word contributes to understanding the tool's purpose.

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 (one parameter, read-only, no output schema) and the strong annotation coverage, the description is largely complete. It clearly states the single operation, and the sibling context suggests alternatives. Minor gap: no explicit mention of return value structure or error behavior, but this is not critical for a get-by-ID 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?

The input schema covers the sole parameter conversationId with a clear description ('Conversation ID'), achieving 100% schema coverage. The tool description adds no additional parameter semantics, so baseline 3 is appropriate.

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 a specific action: 'Get a single conversation by ID with metadata.' It identifies the resource (conversation) and the mode of access (by ID), which distinguishes it from sibling tools like ghl_search_conversations and ghl_get_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?

Usage context is implied: use this tool when you have a specific conversation ID. However, it does not explicitly mention when to use alternatives like ghl_search_conversations or provide exclusions, so guidance is minimal but not misleading.

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