ncloud_hadoop_delete_cluster

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

Adds value beyond annotations: warns of permanent data loss and the need for confirm=true. Annotations already indicate destructiveHint=true, but description emphasizes irreversibility. No contradiction with idempotentHint=true, though idempotency is not discussed.

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?

Extremely concise: single sentence with a leading warning emoji and clear instruction. Every word adds value; no filler.

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?

Sufficient for a destructive delete operation with no output schema: states action, resource, data loss, and required flag. Slightly incomplete by not documenting return value, but typical for delete tools.

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%, so baseline is 3. Description adds context for confirm parameter ('Must be true to execute'), which is critical for correct usage. RegionCode and cloudHadoopInstanceNo are already clearly described in 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?

Clearly states verb 'delete' and resource 'Cloud Hadoop cluster', with explicit warning 'All data will be lost'. Differentiates from sibling delete tools (e.g., ncloud_delete_mongodb_instance) by specifying the resource 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?

Tells when to use (to permanently delete a Hadoop cluster) and explicitly requires confirm=true. Lacks a 'when not to use' statement, but the destructive hint and data loss warning provide sufficient context for an agent to decide.

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