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 of behavioral disclosure. It states 'Create a new output connector definition', which implies a write/mutation operation, but doesn't disclose any behavioral traits such as permissions required, whether the creation is idempotent, rate limits, or what happens on failure (e.g., if the definition already exists). The mention of 'Pass definition as a JSON string' hints at input format but doesn't clarify the response format or success/failure outcomes, leaving significant gaps in understanding the tool's behavior.

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 concise with two sentences that directly address the tool's purpose and a key parameter requirement. It avoids unnecessary words and is front-loaded with the main action. However, it could be slightly improved by integrating the parameter guidance more seamlessly, but overall it's efficient and well-structured for its limited content.

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 creation tool with 2 parameters (one required), 0% schema coverage, no annotations, and an output schema (which exists but isn't detailed here), the description is incomplete. It lacks crucial information: no behavioral context (e.g., permissions, side effects), minimal parameter details, and no mention of the output schema's role. For a mutation tool in a system with many siblings, this leaves the agent under-informed about how to use it effectively.

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 schema provides no descriptions for the two parameters ('body' and 'tenant_id'). The description adds minimal value by specifying that 'body' should be 'a JSON string', which gives some context for one parameter, but doesn't explain what the JSON should contain, its structure, or examples. It doesn't mention 'tenant_id' at all, leaving it completely undocumented. With low coverage, the description fails to compensate adequately for the lack of schema documentation.

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 a new output connector definition') and specifies the resource ('output connector definition'), which is a specific verb+resource combination. It distinguishes from siblings like 'cdp_create_output_connector' (which creates the connector itself rather than its definition) and 'cdp_update_output_connector_def' (which updates rather than creates). However, it doesn't explicitly differentiate from other 'create' tools in the list, such as 'cdp_create_connector' or 'cdp_create_connector_template', which handle different resource types.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether a connector template must exist), when not to use it (e.g., for updates or deletions), or refer to sibling tools like 'cdp_update_output_connector_def' or 'cdp_delete_output_connector_def'. The agent must infer usage from the tool name alone, which is insufficient for clear decision-making.

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