MCP cldkctl 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 of behavioral disclosure. It only states it 'calls an endpoint,' giving no insight into whether this is a destructive mutation (likely, given 'remove'), what permissions are required, if it's idempotent, or what the response looks like. For a tool that presumably modifies registry artifacts, this lack of behavioral context is a significant gap.

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?

While the description is brief, it's under-specified rather than concise. The single sentence 'Call the cldkctl_registry_artifact_remove_label endpoint' wastes space on redundant information (the tool name) without adding value. It fails to front-load useful details, making it inefficient despite its short length.

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 complexity of a registry artifact label removal tool with no annotations and no output schema, the description is completely inadequate. It doesn't explain the tool's purpose, behavior, or usage context, leaving the agent with minimal guidance beyond the parameter schema. For a mutation tool in a registry management context, this lack of completeness is severe.

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 100%, with both parameters ('artifact_id' and 'label_id') clearly documented in the schema. The description adds no additional meaning about these parameters, such as format examples or relationships between them. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, though the description doesn't compensate or enhance parameter understanding.

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 'Call the cldkctl_registry_artifact_remove_label endpoint' is a tautology that restates the tool name without explaining what it does. It mentions 'remove_label' in the name but doesn't specify what resource is being modified (an artifact in a registry) or what the action entails. Compared to siblings like 'cldkctl_registry_artifact_add_label' or 'cldkctl_registry_labels_delete', it fails to distinguish its specific purpose.

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. It doesn't mention prerequisites (e.g., needing an existing artifact and label), when it's appropriate (e.g., to clean up metadata), or what happens after removal. With siblings like 'cldkctl_registry_artifact_add_label' and 'cldkctl_registry_labels_delete', there's no help in choosing between related label management tools.

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