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. 'Deploy' implies a state change (making workflow active), but the description doesn't disclose whether this is reversible, what permissions are required, whether it affects running instances, or what happens if deployment fails. For a mutation tool with zero annotation coverage, this is critically 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 - a single phrase with clarifying parenthetical. Every word earns its place: 'deploy' (action), 'workflow' (resource), 'make it active' (outcome). There's no redundancy or unnecessary elaboration. It's front-loaded with the core purpose.

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 this is a mutation tool with 3 parameters, 0% schema coverage, no annotations, and sibling tools that might overlap (cdp_activate_schedule, cdp_run_workflow), the description is insufficient. While an output schema exists (which helps), the description doesn't address critical context: what 'deploy' means operationally, parameter meanings, or differentiation from similar tools. For a workflow deployment operation, this leaves too many questions unanswered.

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 provides no parameter information. It doesn't explain what workflow_id refers to, what version deployment targets (latest vs specific), or when tenant_id is needed. With 3 parameters (1 required) completely undocumented in both schema and description, this creates significant ambiguity for the agent.

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 ('deploy') and resource ('workflow'), with the parenthetical 'make it active' providing additional semantic context. It distinguishes from sibling tools like cdp_run_workflow (execution) and cdp_get_workflow (retrieval), though not explicitly named. The purpose is specific but could be more differentiated from similar deployment/activation tools.

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 like cdp_activate_schedule or cdp_run_workflow. It doesn't mention prerequisites (e.g., workflow must exist), consequences of deployment, or typical use cases. The agent must infer usage from the name and context alone.

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