ncloud_cdss_list_clusters

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

Annotations declare readOnlyHint=true, and the description does not contradict this. It adds a valuable deprecation warning about cmakPort and cmakVersion fields, which goes beyond the annotation and helps the agent anticipate response inconsistencies. This is strong additional behavioral context.

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 exceptionally concise: two sentences, with the purpose front-loaded and the deprecation warning as a secondary note. Every word adds value, with no redundancy or 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?

For a simple list tool with read-only annotation and full schema coverage, the description covers the core purpose and a notable deprecation detail. It does not describe response structure, but since no output schema is provided and the tool is straightforward, this is acceptable. The deprecation warning adds critical context that an agent would otherwise miss.

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?

All four parameters have schema descriptions (100% coverage), so the baseline is 3. The description mentions 'optional filtering' but does not elaborate on individual parameters, adding no extra semantics beyond what the schema already provides.

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 identifies the service (Cloud Data Streaming Service), the resource (Kafka clusters), and the action (list) with optional filtering. It distinguishes from other list_clusters tools (e.g., ncloud_ses_list_clusters, ncloud_serverless_list_clusters) by naming the specific service, making the purpose unambiguous.

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 specifies the exact resource type, which implicitly tells the agent when to use this tool over other list_clusters tools. However, it does not explicitly mention alternatives or when not to use it, so it falls short of a 5 but provides clear context without exclusions.

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