ncloud_get_block_storage_detail

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

Annotations already mark the tool as readOnlyHint=true, so the description does not need to restate that. However, it provides no additional behavioral context such as rate limits, authentication needs, or what 'detailed information' includes. It adds minimal value beyond 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, well-structured sentence that is immediately understandable. It is front-loaded with the action and resource, containing no unnecessary words or repetition.

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 read tool with one parameter, the description is mostly adequate, but it lacks details about the return value (e.g., what properties are returned). Since there is no output schema, the agent might benefit from knowing the scope of 'detailed information' (e.g., size, state, attachments).

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 parameter description already defines 'blockStorageInstanceNo' as 'Block storage instance number to query'. The tool description adds no extra meaning or nuance to the parameter, so it meets the baseline but does not enhance understanding.

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 states the verb 'Get detailed information' and the resource 'block storage instance', making the tool's purpose immediately obvious. It effectively distinguishes itself from sibling tools like ncloud_list_block_storage by focusing on a specific instance's details.

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 when you have a specific block storage instance number, but it does not explicitly mention when to use this versus alternatives (e.g., listing all instances). There is no guidance on prerequisites or when not to use this tool.

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