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 only states it 'creates a duplicate' without disclosing behavioral traits like whether this is a safe operation, if it requires specific permissions, what happens to the original, or any rate limits. It misses key context for a mutation tool.

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 that front-loads the core action ('Copy a CubicSetDef by ID') and adds clarifying detail ('Creates a duplicate of the OLAP query definition') with zero wasted words.

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?

For a mutation tool with no annotations, 0% schema coverage, but an output schema present, the description is minimally adequate. It states the purpose but lacks behavioral context, parameter semantics, and usage guidelines, though the output schema may cover return values.

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 adds no parameter details. It mentions 'by ID' which hints at 'cubic_set_def_id', but does not explain the purpose of 'tenant_id' or provide any syntax/format guidance beyond what the bare schema offers.

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 ('Copy') and resource ('CubicSetDef by ID'), specifying it creates a duplicate of an OLAP query definition. It distinguishes from siblings like 'cdp_create_cubic_set_def' (create new) and 'cdp_update_cubic_set_def' (modify existing), but does not explicitly mention these alternatives in the description itself.

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 is provided on when to use this tool versus alternatives like creating a new CubicSetDef from scratch or cloning other resources. The description implies usage when duplicating an existing definition, but lacks explicit context or prerequisites.

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