ncloud_cdss_rolling_restart_status

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

Annotations already indicate idempotentHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no additional behavioral context beyond what the annotations provide, such as what progress status looks like or whether it can be polled. It is consistent with 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, focused sentence that directly states the tool's function. Every word earns its place, with no extraneous information or repetition of the tool name.

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 status query with one parameter and clear annotations, the description is minimally adequate. However, there is no output schema, so the description could have explained what the returned progress status looks like or how to interpret it. The lack of return value information leaves a gap for an agent consuming this tool.

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?

The input schema fully describes the single parameter 'serviceGroupInstanceNo' with the description 'Cluster instance number', so schema coverage is 100%. The tool description does not add any further semantic detail about the parameter, but the baseline of 3 is appropriate since the schema carries the burden.

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 identifies the action as 'Get' and the resource as 'progress status of a rolling restart operation'. This distinguishes it from sibling tools like ncloud_cdss_rolling_restart (which initiates the restart) and ncloud_cdss_upgrade_status (which checks upgrade status). However, it could be more explicit about the target cluster or operation context.

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. There is no mention of prerequisites (e.g., after initiating a rolling restart) or exclusions (e.g., not for upgrade status). The description relies entirely on the tool name for context, which is insufficient for an agent deciding between related status tools.

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