ncloud_get_cache_instance_detail

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

Annotations include readOnlyHint: true, which already declares the operation is read-only. The description adds context about the resource type (Redis/Valkey) but does not disclose other behavioral traits such as required permissions, response structure, or potential errors. Since annotations cover the safety profile, this is adequate but not rich.

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 with no extraneous content. It efficiently communicates the essential purpose.

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?

The tool is simple (one well-described parameter, read-only annotation), and the description is sufficient for basic invocation. However, with no output schema, the description doesn't explain what 'detailed information' will be returned or any prerequisites, leaving some context gaps.

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 has one parameter (cloudCacheInstanceNo) with a description 'Cloud Cache instance number to query', covering 100% of the schema. The tool description does not add additional meaning beyond this, so the baseline of 3 applies.

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 a specific action ('Get detailed information') on a specific resource ('a specific Cloud DB for Cache (Redis/Valkey) instance'). It distinguishes itself from sibling tools like ncloud_list_cache_instances (which lists all instances) and other get_*_instance_detail tools by specifying the cache product type.

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 implies use when you have a specific instance number and need details, but it does not explicitly state when to use this versus alternatives, nor does it mention exclusions. For example, it doesn't say to use list_cache_instances for a broad overview or to consult other detail tools for other database types.

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