Genesys Cloud MCP Server

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

Annotations only provide a title, so the description carries the full burden. It discloses behavioral traits such as the structured format (time-aligned list, speaker attribution) and availability of sentiment annotations, which are useful beyond basic retrieval. However, it does not mention potential limitations like rate limits or authentication needs.

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 appropriately sized with two sentences that are front-loaded and efficient. The first sentence states the purpose and key features, and the second elaborates on the format, with no wasted 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?

Given the tool's moderate complexity (single parameter, no output schema, no annotations beyond title), the description is fairly complete. It explains what the tool returns (structured transcript with specific elements), but could benefit from mentioning output format details or any constraints, though the lack of output schema reduces the need for extensive return value explanation.

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%, with the single parameter 'conversationId' well-documented in the schema. The description does not add any additional meaning or context about the parameter beyond what the schema provides, so it meets the baseline of 3.

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 verb 'retrieves' and the resource 'structured transcript of the conversation', with specific details like speaker labels, timestamps, and sentiment annotations. It distinguishes from siblings like conversation_sentiment (which likely focuses only on sentiment) and conversation_topics (which likely focuses on topics), by emphasizing the comprehensive transcript format.

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 usage for retrieving full transcripts, but does not explicitly state when to use this tool versus alternatives like conversation_sentiment or conversation_topics. It provides context by mentioning the structured format, but lacks explicit guidance on exclusions or prerequisites.

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