ncloud_cdss_restart_kafka_per_node

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

The description adds no behavioral detail beyond the annotations. Annotations indicate idempotent and non-destructive, but the description does not disclose side effects like potential service interruption on the specific node, whether the operation is synchronous, or any required prechecks. With annotations present, the bar is lower, but the description still fails to add meaningful 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?

The description is a single, front-loaded sentence that efficiently states the tool's purpose. There is no fluff or redundant information, making it optimally concise for its scope.

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 lack of an output schema and the minimal description, the tool's behavior is under-documented. There is no mention of what happens during the restart, how to verify success, or how this relates to other CDSS restart operations like prechecks or rolling restarts. The context is insufficient for an agent to fully anticipate the tool's effects.

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 both parameters having clear descriptions ('Node compute instance number' and 'Cluster instance number'). The description itself does not add any parameter semantics beyond the schema, so a baseline score of 3 is appropriate.

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 Kafka') and the specific scope ('on a specific node in a CDSS cluster'), which distinguishes it from sibling tools like ncloud_cdss_restart_kafka that presumably restart Kafka cluster-wide. The verb and resource are specific and unambiguous.

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 does not mention that this is for per-node restart, nor does it name alternatives such as ncloud_cdss_restart_kafka for cluster-wide restarts. There is no context about prerequisites or typical use cases.

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