ncloud_hadoop_change_node_count

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description confirms the operation is non-destructive and idempotent but adds no additional behavioral details (e.g., potential downtime, node reassignment, or limits beyond what the schema provides).

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 that is concise, front-loaded with the action, and contains no redundant information. Every word contributes to clarity.

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?

While the description is clear for a simple scaling operation, it omits context such as return values, side effects (e.g., cluster not available during scaling), or constraints like maximum node count. Given the lack of an output schema, this information would be helpful.

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 has 100% coverage with descriptions for all parameters (e.g., workerNodeCount includes 'max +10 per call'). The description adds no parameter-specific meaning beyond what the schema already provides.

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), the resource (worker node count in a Cloud Hadoop cluster), and the scope (add or remove nodes). It effectively distinguishes this tool from sibling Hadoop tools like ncloud_hadoop_create_cluster or ncloud_hadoop_delete_cluster.

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 for scaling worker nodes but does not explicitly state when to use this tool versus alternatives (e.g., changing node specs or creating a new cluster). No prerequisites or exclusion criteria are mentioned.

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