ncloud_cdss_restart_cmak

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds no additional behavioral context (e.g., no mention of downtime, prerequisites, or effects on other services). It is not contradictory but adds minimal value beyond the annotations.

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, concise sentence that directly states the purpose. No extraneous words, front-loaded with the key verb and resource.

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?

For a simple restart operation with one required parameter, the description is adequate but minimal. It does not explain what CMAK is, the effect of restarting, or any preconditions. Since there is no output schema, some additional context about expected results would be helpful.

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 coverage is 100% with a single parameter described as 'Cluster instance number'. The description does not elaborate on the parameter or its usage. Baseline score of 3 is appropriate as the schema already provides sufficient meaning.

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 action ('Restart'), the resource ('CMAK - Cluster Manager for Apache Kafka'), and the scope ('in a CDSS cluster'). This differentiates it from sibling restart tools like ncloud_cdss_restart_all_services, ncloud_cdss_restart_kafka, and ncloud_cdss_restart_kafka_per_node.

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 on when to use this tool versus alternatives. The description implies it is for restarting only the CMAK component, but does not provide a direct comparison or conditions. The context from sibling names helps, but the description itself lacks usage advice.

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