CDP MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively warns about the unsupported endpoint (POST /campaign/audienceDefs) and the expected error (E400 'Request method POST is not supported'), which is crucial behavioral context that would not be captured in annotations alone.

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 front-loaded with the main purpose, followed by critical warnings and alternatives in a logical flow. Every sentence adds value: the first states the intent, the second warns of limitations, and the third provides a workaround with references.

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 unsupported endpoint) and no annotations, the description does well to warn users and suggest alternatives. However, it lacks details on parameters and relies on an external resource link. The presence of an output schema mitigates some gaps in return value explanation.

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%, and the description does not explain the parameters 'body' or 'tenant_id'. It mentions creating an audience definition but provides no details on what the 'body' should contain or the role of 'tenant_id', 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 'audience definition', making the purpose explicit. It distinguishes this tool from siblings like cdp_create_campaign by specifying it creates audience definitions specifically, not campaigns or other resources.

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 explicit guidance on when NOT to use this tool (due to unsupported endpoint returning E400) and offers a clear alternative: define audience inline via cdp_create_campaign + cdp_update_campaign. It also references documentation for further context.

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