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 'Delete' which implies a destructive mutation, but doesn't specify whether this action is reversible, requires specific permissions, has side effects (e.g., cascading deletions), or includes confirmation prompts. For a deletion tool with zero annotation coverage, this is a significant gap in safety and operational context.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action ('Delete'), making it immediately clear, 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 deletion tool with no annotations, 0% schema description coverage, and an output schema (which might provide some return value context), the description is incomplete. It doesn't address behavioral risks, parameter meanings, or usage context, making it inadequate for safe and effective tool invocation by an AI agent.

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%, meaning parameters 'bucket_id' and 'tenant_id' are undocumented in the schema. The description adds no parameter information beyond what's implied by the tool name—it doesn't explain what a bucket_id is, how to obtain it, or when tenant_id is required. With two parameters and no schema descriptions, the description fails to compensate for the coverage gap.

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 'Delete an execution bucket' restates the tool name (cdp_delete_execution_bucket) almost verbatim, making it tautological. It specifies the verb ('Delete') and resource ('execution bucket'), but lacks differentiation from sibling tools like cdp_delete_execution_summary_group or other deletion tools, and doesn't clarify what an 'execution bucket' is in this context.

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 the bucket must be empty or inactive), exclusions, or related tools like cdp_list_execution_buckets for selection or cdp_update_execution_bucket for modifications, leaving the agent with no contextual usage information.

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