ncloud_hadoop_change_node_spec

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds no additional behavioral context, such as potential downtime, authentication needs, or side effects. With annotations present, the description misses the opportunity to provide extra behavioral insight.

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 sentence with no filler, meeting conciseness. It is front-loaded. However, for a tool with 5 parameters, slightly more detail could be added without harming brevity.

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?

The description is minimal and does not explain what happens after upgrading (e.g., reboot, downtime), nor does it provide return value information. Given no output schema, the agent lacks crucial context for correct usage. Sibling tools are not referenced.

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%, with each parameter described. The description adds a meaningful constraint: 'at least one node type required', which is not enforced in the schema (only cloudHadoopInstanceNo is required). This helps the agent understand that at least one product code must be provided.

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 'Upgrade node specs for Cloud Hadoop cluster' with a specific verb and resource. It distinguishes from sibling tools like ncloud_hadoop_change_node_count which changes node count, not spec. However, 'node specs' could be more specific (e.g., server type).

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 provides no guidance on when to use this tool versus alternatives, such as ncloud_hadoop_change_node_count or other Hadoop tools. It does not mention prerequisites, when not to use it, or what to consider before upgrading.

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