CDP MCP Server

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

No annotations are provided, so the description carries the full burden. It states 'Create' implying a write operation, but lacks details on permissions, side effects (e.g., if it sends notifications), rate limits, or error handling. This is a significant gap for a mutation tool with zero annotation coverage.

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 with two sentences, front-loading the core purpose and key requirements. Every word earns its place, with no redundant or verbose language.

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 complexity of a user creation tool with 5 parameters, 0% schema coverage, no annotations, and an output schema (which reduces need for return value explanation), the description is incomplete. It lacks behavioral context, full parameter guidance, and usage distinctions, making it inadequate for safe and effective use.

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. It mentions 'userName and password' as required, covering 2 of 5 parameters, but ignores 'tenant_id', 'first_name', and 'last_name'. This leaves most parameters undocumented, failing to add sufficient meaning beyond the schema.

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 CDP user'), making the purpose explicit. It distinguishes from sibling tools like 'cdp_create_selfservice_user' by specifying a general user creation, though it doesn't explicitly contrast with other user-related tools like 'cdp_update_user' or 'cdp_delete_user'.

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 mentions 'Requires userName and password,' which hints at prerequisites but doesn't provide guidance on when to use this tool versus alternatives like 'cdp_create_selfservice_user' or 'cdp_update_user.' No explicit when/when-not scenarios or sibling tool comparisons are included.

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