CDP MCP Server

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action 'Delete' without specifying if deletion is permanent, reversible, requires confirmation, affects dependencies (e.g., users assigned to the role), or has side effects like audit logging. This leaves critical behavioral aspects undocumented.

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, direct sentence with no wasted words, making it highly concise. It is front-loaded with the core action, though this brevity contributes to underspecification in other dimensions.

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 (a destructive deletion operation with 2 parameters), lack of annotations, 0% schema description coverage, and presence of an output schema (which the description does not reference), the description is severely incomplete. It fails to address safety, parameters, outcomes, or integration with sibling tools, leaving the agent poorly informed.

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 by explaining parameters. It mentions 'by ID' but does not clarify the 'role_id' parameter's format, valid ranges, or the optional 'tenant_id' parameter's purpose (e.g., multi-tenancy context). No additional semantic meaning is provided beyond the schema's basic 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 'Delete a role by ID' restates the tool name 'cdp_delete_role' with minimal elaboration, making it tautological. It specifies the verb 'Delete' and resource 'role', but lacks detail on scope (e.g., permanent vs. soft deletion) or system context, and does not differentiate from sibling deletion tools like 'cdp_delete_user' or 'cdp_delete_schedule'.

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 (e.g., 'cdp_update_role' for modification, 'cdp_list_roles' for viewing), prerequisites (e.g., role must exist, user permissions), or exclusions (e.g., cannot delete default roles). The description offers no contextual usage information.

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