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 execution bucket', which implies a write operation, but doesn't disclose any behavioral traits such as required permissions, whether this is idempotent, what happens on failure, or if there are rate limits. The mention of 'configuration as a JSON string' hints at input format but doesn't explain the expected structure or constraints. For a creation tool with zero annotation coverage, this leaves significant gaps.

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 short sentences that are front-loaded and waste no words. It directly states the action and key input requirement without unnecessary elaboration, making it efficient and easy to parse.

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's complexity (creation operation with 2 parameters), no annotations, and an output schema (which reduces the need to describe return values), the description is incomplete. It covers the basic purpose but lacks usage guidelines, behavioral details, and parameter semantics. While the output schema helps, the description doesn't provide enough context for safe and effective use, especially for a write operation with undocumented parameters.

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?

The description mentions 'configuration as a JSON string', which loosely maps to the 'body' parameter, but doesn't explain what this configuration entails or provide any details about the 'tenant_id' parameter. With schema description coverage at 0% and 2 parameters (one required), the description adds minimal value beyond the schema's property names. It fails to compensate for the lack of schema descriptions, leaving parameters largely undocumented.

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 'Create' and the resource 'execution bucket', making the purpose specific and understandable. It distinguishes from siblings like cdp_list_execution_buckets (list vs. create) and cdp_update_execution_bucket (update vs. create), though it doesn't explicitly differentiate beyond the inherent action. The mention of 'configuration as a JSON string' adds useful detail about the input format.

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, such as whether an execution bucket is needed for specific workflows, or when to choose this over other creation tools like cdp_create_execution_summary_group. The only implied usage is for creating execution buckets, but no context or exclusions are stated.

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