ncloud_ses_get_node_storage

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

readOnlyHint=true already establishes this as a safe read, so the description need not repeat that. It does add one genuinely useful constraint beyond the annotations, the 'Public zone only' scope, but says nothing about the shape of the returned storage data or whether a node can have zero attached volumes.

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, front-loaded with the action and resource, with the prerequisite and the zone constraint following. No filler.

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 one-parameter read-only lookup with no output schema, the description supplies the key facts an agent needs: what is returned, where the identifier comes from, and the zone restriction. Only the absence of any return-shape hint keeps it from a 5.

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?

With a single parameter at 100% schema coverage, the schema already documents computeInstanceNo and even names ncloud_ses_get_node_list as its source. The description repeats that provenance rather than adding format or validation detail, so the baseline 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?

Specific verb ('Get') plus a precise resource ('block storage attached to a Search Engine Service cluster node'), which is more than a restatement of the name. It implicitly differentiates from the near-identical sibling ncloud_cdss_get_node_storage by naming the SES product, though it never states that distinction explicitly.

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 parenthetical pointing to ncloud_ses_get_node_list tells the agent where to obtain computeInstanceNo, and 'Public zone only' scopes when the tool is valid. There is no explicit when-to-use vs. alternative guidance beyond that.

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