ncloud_hadoop_create_cluster

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

Beyond annotations (only destructiveHint: false), the description discloses that HA is always enabled with 2 master nodes and mentions dryRun for preview. This adds behavioral context not captured in annotations, though it could elaborate on other behaviors like billing or process duration.

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?

Two sentences, front-loaded with the purpose, and zero wasted words. 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 tool with 29 parameters (14 required), the description is too brief. It omits important context like needing VPC, subnets, or referencing other tools (e.g., ncloud_hadoop_list_cluster_types) to determine parameters. The dryRun tip is helpful, but overall incomplete.

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%, so the schema already documents parameters. The description adds slight value by highlighting dryRun usage, but doesn't explain any parameter relationships or constraints beyond schema.

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 tool creates a Cloud Hadoop cluster with a specific verb and resource. It also adds key details like HA always enabled and dryRun preview, which distinguishes it from sibling tools like 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?

Provides a specific usage tip (use dryRun=true to preview), but lacks guidance on prerequisites, when to use versus alternatives, or when not to use. Minimal guidance overall.

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