ncloud_datafence_get_hadoop_cluster

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds no further behavioral context such as return format, pagination, permissions, or what 'details' actually includes, so it provides essentially no value beyond the structured annotation.

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?

A single front-loaded sentence with zero waste. It is appropriately sized for a simple get-by-IDs operation and every word earns its place.

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 simple read tool with full schema coverage and readOnly annotations, the description is minimally adequate: it names the operation and resource. However, it does not clarify what details are returned or how this tool relates to the similarly named Hadoop cluster detail tool, leaving a small but real contextual gap.

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%, and the schema itself cross-references sibling tools ('see ncloud_datafence_list_boxes', 'see ncloud_datafence_get_datafence') and explains 'hadoopClusterNo'. The description adds no parameter meaning beyond that, so baseline 3 is appropriate.

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?

States a specific verb ('Get') and resource ('Box Hadoop cluster's details'), so the operation is clear. However, it does not distinguish this tool from the similarly named sibling 'ncloud_hadoop_get_cluster_detail' or other get-detail tools, leaving ambiguity about when this Datafence-specific variant is the right choice.

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 no when-to-use guidance, no prerequisites, and no alternatives. It does not tell the agent to use this tool only for clusters inside a Datafence Box, nor how it differs from 'ncloud_hadoop_get_cluster_detail'.

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