CDP MCP Server

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

No annotations are provided, so the description carries full burden. It only states 'Create a new connector definition' without disclosing any behavioral traits: no information about permissions required, whether this is a mutating operation (implied but not confirmed), rate limits, idempotency, or what happens on success/failure. This is inadequate for a creation 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?

Extremely concise with two sentences that directly address the core action and parameter format. No wasted words, though this brevity contributes to the lack of detail in other dimensions.

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 a creation tool with 2 parameters (0% schema coverage), no annotations, and an output schema (which helps but doesn't excuse the description), the description is incomplete. It fails to explain parameter semantics adequately, provides no behavioral context, and offers no usage guidance, making it insufficient for reliable tool invocation.

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 'Pass definition as a JSON string' which partially explains the 'body' parameter, but doesn't clarify the JSON structure or purpose. The 'tenant_id' parameter is completely undocumented in both schema and description. The description adds minimal value beyond the bare 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 states the verb ('Create') and resource ('connector definition'), but is vague about what a 'connector definition' entails. It distinguishes from siblings like 'cdp_create_connector' by specifying 'template', but doesn't clarify the difference between a connector and a connector template, leaving purpose somewhat ambiguous.

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 like 'cdp_create_connector' or 'cdp_create_mapping_template'. The description provides no context about prerequisites, typical use cases, or exclusions, leaving the agent with no usage direction.

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