ncloud_cdss_get_node_storage

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

Annotations already declare readOnlyHint=true, and the description adds a genuine behavioral constraint not present in structured data: availability is limited to Public and Financial zones. It does not describe the returned block-storage payload, but the annotation covers the safety profile.

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?

Two short sentences with zero filler; the action is front-loaded and the source-tool pointer and zone constraint are packed into the remainder. Every clause earns its place.

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 one fully documented parameter, a read-only annotation, and no output schema, the definition is nearly sufficient for correct invocation. The only omission is any indication of the shape or pagination of the returned block-storage records.

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% and the single parameter is fully documented in the schema, including the same 'from ncloud_cdss_list_nodes' pointer. The description therefore adds no meaning beyond the schema, so the baseline 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 gives a specific verb and resource ('Get the block storage attached to a CDSS cluster node'), which is unambiguous and clearly distinct from the similarly named ncloud_ses_get_node_storage. It does not, however, explicitly contrast itself with that sibling, so it falls just short of the top tier.

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?

It tells the agent where the required identifier comes from ('computeInstanceNo from ncloud_cdss_list_nodes') and scopes applicability with 'Public and Financial zones only'. There is no explicit when-not-to-use or alternative routing, but the context is clear.

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