ncloud_datafence_change_fence_nas_volume

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

Annotations declare idempotentHint=true and destructiveHint=false, covering the safety profile. Beyond that, the description adds the step-size behavior (100 GB steps) not present in the schema, but says nothing about downtime, whether shrinking is allowed, or service impact during resize.

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?

A single front-loaded sentence that states the action and the key constraint with no wasted words. Efficient and immediately actionable.

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 mutation tool with full schema coverage and annotations covering safety/idempotency, the description is minimally adequate. It omits operational context a resizing operation would benefit from, such as whether a restart is required or whether volume size can be decreased.

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 description coverage is 100% and both min/max bounds already appear in the schema. The description adds the 100 GB step increment, a useful constraint absent from the schema, but otherwise adds little beyond what the parameters already document. Baseline 3 is appropriate.

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?

States a specific verb+resource: 'Resize a Datafence NAS volume'. This is clear and unambiguous about what the tool does, but it does not distinguish itself from siblings like ncloud_datafence_change_box_nas_volume or ncloud_change_nas_volume_size, which an agent must tell apart.

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 gives no when-to-use guidance, no prerequisites, and no mention of when to prefer this over the sibling change_box_nas_volume or nas_volume_size tools. Usage must be inferred entirely from the name.

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