ncloud_cdss_rolling_restart

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

Annotations already indicate idempotentHint=true and destructiveHint=false, so the description's 'rolling restart' adds context about gradual, non-destructive behavior. However, it does not elaborate on impact, health checks, or whether the operation is safe to run multiple times.

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, focused sentence with no fluff. It efficiently conveys the core action 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?

Given the simplicity of the tool (one required parameter, no output schema), the description is mostly complete. It could mention that the cluster must already exist, but for an experienced user, it is sufficient.

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% (one parameter described). The description reiterates 'CDSS cluster' but adds no new meaning beyond the schema's 'Cluster instance number'. 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?

The description uses a specific verb ('Perform a rolling restart') and clearly identifies the resource ('all nodes in a CDSS cluster'). It distinguishes from sibling tools like ncloud_cdss_restart_all_services and ncloud_cdss_restart_kafka_per_node by specifying 'rolling' and 'all nodes'.

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 is provided on when to use this tool versus alternatives such as ncloud_cdss_restart_all_services or ncloud_cdss_restart_kafka_per_node. There is no mention of prerequisites, preconditions, or when not to use it.

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