ncloud_cdss_restart_kafka

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

Annotations already declare idempotentHint=true and destructiveHint=false, covering safety. Description adds that it restarts both Kafka and ZooKeeper services, but does not disclose important traits like scope (all nodes?), potential downtime, or ordering. With annotations, the description provides adequate but not rich behavioral context.

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?

Description is a single, succinct sentence of 9 words with no wasted words. It is front-loaded and immediately conveys the core function. Every word earns its place.

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?

Despite low complexity (one param, no output schema), the description omits critical details: scope (all nodes? rolling?), impact on clients, prerequisites, and whether it is safe or causes downtime. A restart operation should at least hint at these aspects to guide the agent.

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%: the only parameter serviceGroupInstanceNo has description 'Cluster instance number'. The tool description does not add any further meaning beyond what the schema provides, so baseline score of 3 applies.

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?

Description clearly states 'Restart Kafka and ZooKeeper services in a CDSS cluster', specifying the verb (restart) and exact resources (Kafka and ZooKeeper services) within a CDSS cluster. This distinguishes it from sibling tools like ncloud_cdss_restart_all_services 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?

Description provides no guidance on when to use this tool versus alternatives such as ncloud_cdss_restart_all_services or ncloud_cdss_restart_kafka_per_node. There are no explicit usage contexts, prerequisites, or exclusions mentioned.

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