ncloud_hadoop_list_clusters

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

The annotation readOnlyHint=true already covers the safety profile of this read operation. The description adds only 'with optional filtering', which is a minimal behavioral trait already implied by the optional schema parameters. No additional context is provided about pagination defaults, response shape, or account/region scope, though the schema documents pageNo/pageSize defaults.

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 concise sentence, front-loaded with the verb 'List'. Every word earns its place, with no redundancy or filler. It is appropriately sized for a straightforward list tool.

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?

The tool has 10 optional parameters and no output schema, yet the description does not mention return value structure or pagination behavior beyond what the schema provides. It is minimally sufficient for a list operation, but gaps exist around default page size (1, which is unusual) and what cluster fields are returned. Given the tool's simplicity and high schema coverage, a score of 3 reflects adequacy with clear gaps.

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%, with all 10 parameters documented in the schema. The description adds no parameter-specific meaning beyond the generic 'optional filtering' statement. Per the evaluation rule, a high-coverage schema sets a baseline of 3, which is appropriate here.

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 states a specific verb and resource: 'List Cloud Hadoop clusters'. The phrase 'with optional filtering' clarifies the tool's scope and distinguishes it from detail-oriented siblings like ncloud_hadoop_get_cluster_detail. The service name 'hadoop' in both tool name and description distinguishes it from other list_clusters tools (e.g., ncloud_nks_list_clusters).

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?

No guidance is provided on when to use this tool vs alternatives such as ncloud_hadoop_get_cluster_detail or ncloud_hadoop_list_cluster_types. There is no mention of prerequisites, pagination usage, or recommended filters. The description only states what it does, leaving the agent to infer usage from the name and schema.

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