ncloud_hadoop_create_cluster

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

The description discloses that HA is always enabled (2 master nodes) and that dryRun provides a preview, adding useful context beyond the destructiveHint annotation. However, it does not cover other behavioral aspects like asynchronous creation, expected wait times, or post-creation status, so transparency is only partially addressed.

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 three short sentences, each contributing a distinct piece of information: the action (create), a key characteristic (HA with 2 master nodes), and a usage tip (dryRun). There is no fluff or repetition, making it highly efficient.

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 complex 29-parameter creation tool with no output schema, the description is minimal. It provides high-level context (HA, dryRun) and the schema fills parameter-level detail, but it lacks guidance on workflows like listing cluster types, checking login keys, or what to do after creation. The description is adequate but not complete for the tool's complexity.

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?

Although the schema covers all parameters with descriptions (100% coverage), the description adds meaning beyond the schema: it explains that HA is forced (so no master node count parameter is needed) and clarifies the dryRun parameter's purpose as a preview mode. This extra context aids parameter 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 'Create a new Cloud Hadoop cluster' with a specific verb and resource. It adds a distinguishing detail (HA always enabled, 2 master nodes) and mentions dryRun, making the tool's intent unambiguous even among many sibling tools.

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 the tool is used when a Cloud Hadoop cluster needs to be created, but it does not explicitly compare to alternatives or state prerequisites such as needing VPC subnets or consulting cluster type lists. The only usage hint is 'Use dryRun=true to preview', which applies to invocation rather than tool selection.

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