CDP MCP Server

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions the JSON format for user details but doesn't disclose permissions needed, whether this is a mutating operation (implied by 'Create'), rate limits, error conditions, or what happens on success/failure. For a user creation tool with zero annotation coverage, this is inadequate.

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 extremely concise—two brief sentences with zero wasted words. It's front-loaded with the core purpose and follows with a critical implementation detail. Every sentence earns its place.

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 creates a user (a significant mutation), has no annotations, 0% schema description coverage, but does have an output schema (which reduces need to describe returns), the description is minimally complete. It states the action and data format but lacks crucial context like permissions, validation rules, or error handling, making it barely adequate for a mutation 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%, so the description must compensate but only partially does. It mentions 'user details as a JSON string' which loosely maps to the 'body' parameter, but doesn't explain what fields the JSON should contain, format examples, or the optional 'tenant_id' parameter's purpose. Two parameters exist with no schema descriptions, and the description adds limited value.

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 ('Create') and resource ('new self-service user'), making the purpose explicit. It distinguishes from siblings like 'cdp_create_user' by specifying 'self-service' user type, though it doesn't explicitly contrast them.

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 is provided on when to use this tool versus alternatives like 'cdp_create_user' or 'cdp_update_selfservice_user'. The description only states what it does, not when it's appropriate or what prerequisites might exist.

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