ncloud_ses_change_disk_size

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

The description does not provide any behavioral context beyond what the annotations already indicate (idempotentHint=true, destructiveHint=false). It does not mention potential downtime, prerequisites, or the fact that this is a mutating operation on a cluster. Since annotations only cover safety profile, the description adds little value here.

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, front-loaded sentence with no unnecessary words. It directly states the verb and object, making it highly concise and easy to parse.

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 two-parameter tool with full schema documentation and safety annotations, the description is minimally sufficient. However, it lacks context about the operational impact (e.g., whether the cluster reboots or if there is any downtime), which would be valuable for an agent deciding to invoke it. There is no output schema to compensate, so the description alone does not fully cover the operational picture.

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?

The input schema already provides complete coverage (100%) for both parameters, including type, range, and increment details for dataNodeStorageSize. The description does not add any extra semantic meaning beyond the schema, so the baseline score of 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?

The description clearly states the action ('Change') and the specific resource ('data node disk capacity') within a Search Engine Service cluster. It is sufficiently distinct from sibling tools like ncloud_ses_change_node_spec or ncloud_ses_add_node, which target different aspects of cluster configuration.

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 context of use is clear: this tool is for changing the disk capacity of data nodes in an SES cluster. However, it does not explicitly mention alternatives or exclusionary conditions, such as 'use this instead of change_node_spec when only disk size needs adjustment.'

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