ncloud_cdss_rolling_restart_precheck

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

Annotations already indicate idempotentHint=true and destructiveHint=false, so the description carries a lower burden. The phrase 'Pre-check' aligns with these hints but adds no extra behavioral context, such as what the check entails, what it returns, or whether it is a required gate before 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?

The description consists of a single, lean sentence that directly states the tool's purpose. There is no fluff, repetition, or unnecessary detail, making it highly efficient and front-loaded.

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?

With no output schema, the description should explain what the pre-check result looks like or how to interpret it, but it doesn't. It also lacks mention of preconditions or relationship to the rolling restart flow. For a simple one-parameter tool, it is minimally viable but has clear informational gaps.

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 already provides 100% coverage for the only parameter, serviceGroupInstanceNo, with a description 'Cluster instance number'. The tool description adds no additional meaning beyond the schema, so the 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 'Pre-check before performing a rolling restart' clearly identifies the tool as a pre-check for a specific operation. It uses a specific verb-resource pairing and distinguishes it from siblings like ncloud_cdss_rolling_restart and ncloud_cdss_rolling_restart_status, though it doesn't detail what exactly is checked.

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 does not explicitly state when to use this tool vs alternatives. It implies it should be used before a rolling restart but gives no explicit guidance, exclusions, or comparison to related tools like ncloud_cdss_rolling_restart_status or ncloud_cdss_upgrade_precheck.

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