Genesys Cloud MCP Server

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

Annotations provide a title ('List OAuth Clients') but no other hints. The description adds that it retrieves 'all' OAuth clients and mentions the organizational scope ('Genesys Cloud organization'), which is useful context beyond annotations. However, it lacks details on pagination, rate limits, or authentication requirements.

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 two concise sentences: the first states the purpose and scope, the second provides usage context. Every sentence adds value without redundancy, and it is front-loaded with the core functionality.

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 simplicity (0 parameters, no output schema), the description is complete enough for a read-only list operation. It covers purpose, scope, and usage context. However, without annotations or output schema, it could benefit from more behavioral details like response format or limitations.

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 has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, maintaining focus on the tool's purpose and usage.

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 resource ('list of all OAuth clients'), specifying what data is included ('associated roles and divisions'). It distinguishes from siblings like 'oauth_client_usage' by focusing on listing clients rather than usage metrics.

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 provides clear context for when to use this tool ('useful for auditing and managing OAuth clients'), but does not explicitly state when not to use it or name alternatives. It implies usage for administrative purposes without specifying exclusions.

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