ncloud_hadoop_list_clusters

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

The annotations already declare readOnlyHint=true, and the description does not contradict this. It adds the notion of 'optional filtering', which is minor. No further behavioral details (e.g., pagination, performance) are disclosed. Given the annotations, the description provides minimal additional transparency.

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 sentence with 6 words, conveying the core purpose and filtering capability without redundancy. It earns its place and is front-loaded.

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. The description is minimal, lacking details about default behavior, output format, or pagination. For a list tool with complex filtering, a bit more context would be helpful, but the schema covers parameter usage, making it adequate.

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?

The input schema has 100% description coverage for all 10 parameters. The description only summarizes 'optional filtering' without adding parameter-specific details. Baseline 3 is appropriate as the schema already defines all parameter semantics.

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 verb 'List' and the resource 'Cloud Hadoop clusters', and mentions optional filtering. Among sibling tools, it uniquely identifies this tool for listing Hadoop clusters, distinguishing it from other Hadoop list tools like ncloud_hadoop_list_addons or ncloud_hadoop_list_buckets.

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 usage for listing clusters with optional filtering, but does not explicitly state when to use this tool over alternatives or provide any exclusions. For a read-only list tool, this level of guidance is adequate but not explicit.

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