ncloud_cdss_restart_kafka_per_node

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

Annotations already indicate idempotent and non-destructive behavior. The description adds that it operates on a specific node, which is consistent with annotations. However, it does not disclose potential impact (e.g., service disruption during restart).

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?

Single sentence, front-loaded with the essential action. No unnecessary information, but could benefit from a slightly more structured format (e.g., listing parameters).

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?

Basic completeness given the simple tool: two parameters, no output schema. Lacks context about expected behavior during restart, whether it is graceful, or how it differs from other restart tools.

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?

Input schema has 100% description coverage for both parameters (serviceGroupInstanceNo and computeInstanceNo). The tool description does not add any additional meaning beyond what is already in the schema.

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 (Kafka on a specific node), and the context (CDSS cluster). It distinguishes from sibling tools like ncloud_cdss_restart_kafka (global restart) and ncloud_cdss_restart_all_services.

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 on when to use this tool versus alternatives like ncloud_cdss_restart_kafka or ncloud_cdss_rolling_restart. No prerequisites or use cases mentioned.

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