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. It indicates a creation action (implying mutation) but doesn't disclose behavioral traits like required permissions, side effects, rate limits, or what happens on success/failure. The mention of 'POST /v2/{tenantId}/mailer/batches' hints at an HTTP method but lacks 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 brief and front-loaded with the core action. It wastes no words, though it could be more informative. The single sentence efficiently states the tool's basic function and parameter format.

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 has 2 parameters with 0% schema coverage, no annotations, and an output schema (which helps but isn't described), the description is incomplete. It lacks details on parameter semantics, behavioral context, and usage guidelines, making it inadequate for a mutation tool in a complex system.

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. It mentions passing 'the definition as a JSON string' for the 'body' parameter, which adds some meaning, but doesn't explain the structure or content of that JSON or the purpose of 'tenant_id'. With 2 parameters and low schema coverage, this is insufficient.

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 verb ('Create') and resource ('a mailer batch'), which clarifies the basic purpose. However, it doesn't specify what a 'mailer batch' is or how it differs from sibling tools like 'cdp_process_mailer_batch' or 'cdp_update_mailer_batch', leaving the purpose somewhat vague.

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. The description mentions the API endpoint but doesn't explain prerequisites, dependencies, or scenarios where this tool is appropriate compared to other mailer-related tools in the sibling list.

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