ncloud_cdss_get_cluster_detail

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

The annotation already indicates readOnlyHint=true, so the tool is a read operation. The description adds no further behavioral context, such as what specific details are returned (e.g., configuration, brokers, nodes), whether it triggers any side effects, or if it has rate limits. For a read operation, minimal transparency is acceptable, but it could be improved.

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 concise—one sentence that efficiently conveys the purpose. It is front-loaded with the key information. No unnecessary words. It could be slightly more informative without becoming verbose, but it meets the standard for a simple read 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?

Given the simplicity of the tool (1 parameter, no output schema), the description is somewhat complete. However, it lacks details about what 'detailed information' includes (e.g., cluster properties, node list, configuration) and does not contrast with similar detail tools for other services. With no output schema, the description should provide more context about the return value.

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 coverage is 100% for the single parameter 'serviceGroupInstanceNo', and the schema description is adequate ('Cluster instance number from cluster list'). The tool description does not add any additional meaning or context beyond the schema, so a baseline score of 3 is appropriate.

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 ('get detailed information') and the resource ('a specific CDSS (Kafka) cluster'). It distinguishes itself from sibling tools like ncloud_cdss_list_clusters (which lists clusters) and ncloud_cdss_get_cluster_status (which only gets status) by using 'detailed information'.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., obtaining the cluster instance number from a list) or suggest use cases. Sibling tools that list clusters or get status are not referenced.

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