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 mentions the tool performs a POST operation (implying a write/mutation) and describes the endpoint structure, but lacks critical behavioral details like authentication requirements, rate limits, error handling, or what constitutes a successful event post. This is a significant gap for a mutation tool with zero annotation coverage.

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 efficiently structured in two sentences: the first states the purpose and endpoint, the second details parameter usage. Every sentence provides essential information with zero waste, making it easy to parse front-loaded key details.

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 an output schema (which handles return values), no annotations, and 3 parameters with 0% schema coverage, the description adequately covers the purpose and parameters but lacks behavioral context for a mutation tool. It's minimally viable but leaves gaps in usage guidelines and transparency.

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, the description compensates well by explaining all three parameters: 'body' as a JSON string with required fields (eventType, identityHash, properties), 'api_version' as a routable path segment with default 'v2', and 'tenant_id' as part of the endpoint path. It adds meaningful context beyond the bare schema types.

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 specific action ('Post a real-time tracking event'), target resource ('to the CDP'), and method (HTTP POST with endpoint path). It distinguishes itself from sibling tools by focusing on event tracking rather than cache operations, audience calculations, or other CDP functions listed.

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 explicit guidance is provided on when to use this tool versus alternatives. While the description mentions the API endpoint and parameter defaults, it doesn't specify use cases, prerequisites, or exclusions. The agent must infer usage from the purpose alone.

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