ncloud_cdss_list_clusters

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

The annotation readOnlyHint=true already indicates a safe read operation, so the description does not need to restate that. However, the description adds no additional behavioral information such as pagination, response structure, or any limits. It simply restates the tool's purpose without disclosing side effects or 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 a single, front-loaded sentence containing only necessary information. It concisely states the verb, resource, and capability without any fluff or redundancy.

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?

There is no output schema, so the description should explain what the tool returns (e.g., cluster summaries, paginated list). It does not. It also does not mention that results are paginated, which is implied by the pageNo and pageSize parameters. For a list tool with no output schema, the description is incomplete.

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 schema covers all four parameters with descriptions that already include defaults (pageNo, pageSize) and match types (exact match for vpcName, partial match for inputText). The tool description adds no additional parameter meaning beyond saying 'optional filtering', so it does not compensate beyond the schema's high coverage.

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 action (List) and resource (Cloud Data Streaming Service (Kafka) clusters), and adds the scope 'with optional filtering'. It distinguishes from siblings by naming the specific service, though it could more explicitly differentiate from related tools like get_cluster_detail or get_cluster_status.

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 explicit guidance on when to use this tool versus alternatives. It implies usage for listing clusters but does not mention that get_cluster_detail is for a single cluster or that this tool returns a summary list. No exclusions or alternative tool names are provided.

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