get_conversation_detail

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

No annotations are provided, so the description must disclose behavioral traits. It does not state whether the tool is read-only, required permissions, or any side effects. The mention of 'complete messages' and 'customer data' is vague, and pagination (via limit/offset) is not mentioned in the description.

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 short sentence with a dash, making it efficient and front-loaded with the verb and resource. However, the use of a dash and the unclear '[query]' slightly detract from clarity.

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 13 parameters, no output schema, and no annotations, the description is too brief. It does not explain the two alternative ways to identify a conversation (phone vs. conversation_id), the meaning of limit/offset for pagination, or the specific customer data fields returned. The tool requires more context for correct usage.

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 100%, so the baseline is 3. The description adds little beyond the schema: it mentions 'customer data' but does not explain how parameters like phone and conversation_id serve as alternative identifiers, nor does it clarify the use of limit/offset for pagination.

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 'Show detail of conversation' and mentions showing complete messages and customer data. It identifies the tool's purpose, but the trailing '[query]' is ambiguous and the tool's scope relative to siblings like 'search_conversations' is not differentiated.

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?

No guidance on when to use this tool versus alternatives such as 'get_recent_conversations', 'get_conversation_analytics', or 'search_conversations'. The description merely implies use for fetching full conversation details but lacks any context about prerequisites or 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.