ncloud_get_fabric_cluster_detail

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds minimal context by specifying 'specific' (implying a single cluster), but does not disclose response details, error behavior, or required permissions beyond what annotations imply. It is consistent with the annotation.

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 of nine words, directly stating the purpose with no fluff or redundancy. It is front-loaded and every word contributes.

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 read-only tool with one parameter, the description is adequate for basic invocation. The schema covers the parameter and annotations cover safety. However, it lacks guidance on what 'detailed information' includes or how to find the cluster number, which could be helpful for an agent.

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 a descriptive parameter name and description ('Fabric cluster number to query'). The tool description does not add any extra meaning about the parameter's format, source, or usage 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 states the tool's function: 'Get detailed information about a specific fabric cluster.' It uses a specific verb and resource and distinguishes from listing tools like ncloud_list_fabric_clusters by focusing on a single cluster. However, it does not explicitly name alternatives or clarify the relationship to sibling tools like ncloud_get_fabric_cluster_pools.

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 how to obtain the fabricClusterNo, whether to use it after listing clusters, or any prerequisites. There is no exclusionary or comparative language.

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