ncloud_cdss_list_clusters

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

The description adds 'with optional filtering' but does not elaborate on filtering behavior beyond what the input schema provides. Annotations declare readOnlyHint=true, which is consistent. No additional behavioral traits like pagination limits or rate limiting are disclosed.

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 that conveys the essential purpose without unnecessary words. No redundancy or verbosity.

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 well-documented parameters, the description is nearly complete. It could mention that results are paginated (given pageNo/pageSize parameters) or describe the output format, but the absence of an output schema means the agent relies on the API response structure. Still, it's sufficiently informative.

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% coverage with descriptive parameter descriptions. The tool description only says 'optional filtering', which adds no new meaning. Baseline 3 is appropriate since the schema does the heavy lifting.

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 explicitly states the verb 'List' and the resource 'Cloud Data Streaming Service (Kafka) clusters', which clearly distinguishes it from other cluster listing tools like ncloud_hadoop_list_clusters or ncloud_ses_list_clusters. The mention of 'optional filtering' adds specificity.

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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. While the resource name implies CDSS clusters, no direct comparison or exclusion criteria are given. This is adequate but not proactive.

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