ncloud_create_cache_instance

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

The description discloses the non-destructive preview behavior via dryRun, which adds value beyond the destructiveHint annotation. It clearly states that the tool creates an instance, and the dryRun hint provides an important safety behavior. It does not mention async behavior or billing, but the core create semantics are transparent.

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?

Two concise sentences. The first states the primary purpose with a clear verb and resource; the second adds a crucial safety tip. No filler or redundant information.

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 15-parameter create tool, the description is minimal. It gives the essential purpose and dryRun guidance, but does not explain return values (there is no output schema) or high-level configuration guidance (e.g., cluster mode). The schema covers individual parameters, but the description alone is borderline sufficient.

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 description coverage is 100%, so the baseline is 3. The description does mention dryRun, but the schema already thoroughly explains that parameter ('If true, returns a preview without actually creating the instance'). No additional parameter semantics are added beyond the schema.

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 uses a specific action ('Create') and a specific resource ('Cloud DB for Cache (Redis/Valkey) instance'), clearly distinguishing it from sibling instance creation tools for MySQL, Postgres, MongoDB, etc. It also highlights the unique dryRun preview feature.

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 context is clear: this is for creating a Cache (Redis/Valkey) instance. It provides a concrete usage tip (use dryRun=true to preview), which implies a safe workflow. It doesn't explicitly exclude alternative tools, but the resource specificity makes the intended use obvious.

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