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 for behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't mention permissions required, whether this is idempotent, what happens on failure, rate limits, or what the output contains. The JSON configuration requirement is mentioned but without context about what configuration options exist.

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 appropriately brief with two clear sentences. The first states the action, the second provides parameter guidance. There's no unnecessary verbosity, though it could benefit from being more informative while maintaining conciseness.

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 creation tool with 2 parameters (one required), 0% schema coverage, no annotations, and sibling tools that suggest this is part of a larger system, the description is inadequate. While an output schema exists, the description doesn't provide enough context about what an 'execution summary group' is, what configuration it accepts, or how it fits into the broader CDP ecosystem.

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?

With 0% schema description coverage for 2 parameters, the description only partially compensates. It mentions that 'configuration' should be passed as a JSON string (mapping to 'body'), but provides no details about what configuration options exist or their format. The 'tenant_id' parameter is completely undocumented in both schema and description.

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 states the action ('Create a new execution summary group') which is a clear verb+resource combination. However, it doesn't explain what an 'execution summary group' is or how it differs from sibling tools like 'cdp_create_execution_bucket' or 'cdp_list_execution_summary_groups', leaving the purpose somewhat vague for someone unfamiliar with the system.

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. There's no mention of prerequisites, when this creation operation is appropriate, or how it relates to similar tools like 'cdp_update_execution_summary_group' or 'cdp_delete_execution_summary_group'.

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