ncloud_cdss_upgrade_status

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

No annotations provided; the description merely states it returns progress status. It does not disclose whether the operation is safe to call repeatedly, any rate limits, or permissions needed. For a read-only status check, more transparency on polling behavior or expected response could be added.

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, 9 words, no filler. Every word contributes to the purpose. Ideally concise 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?

For a simple status retrieval with no output schema, the description is adequate but doesn't hint at the response structure (e.g., what fields are returned). Lacks details that would help the agent interpret the result, but given low complexity, a score of 3 is fair.

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 one parameter 'serviceGroupInstanceNo' described as 'Cluster instance number'. Description adds no additional meaning beyond the schema; it doesn't explain how to obtain the instance number or its format, but schema alone suffices for the basic parameter.

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?

Description uses specific verb 'Get' and resource 'progress status of a version upgrade operation'. Clearly distinguishes from sibling tools like ncloud_cdss_upgrade_version (which initiates upgrade) and ncloud_cdss_upgrade_precheck (which checks feasibility before upgrade). No ambiguity.

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 implies usage after initiating a version upgrade, but does not explicitly state when to use this tool vs. alternatives like ncloud_cdss_rolling_restart_status or ncloud_cdss_get_cluster_status. No mention of prerequisites or 'when not to use'.

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