ncloud_create_mssql_instance

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

Annotations provide destructiveHint: false, indicating a non-destructive operation. The description adds the dryRun preview feature, which is useful behavioral context. However, it does not disclose other behaviors such as time to completion, idempotency, or whether the creation is irreversible. Given the annotations, the description adds some value but lacks depth.

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 extremely concise with two sentences. The first sentence front-loads the core purpose, and the second adds a critical usage hint (dryRun). No extraneous information is present.

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 tool's complexity (20 parameters, no output schema), the description is notably incomplete. It does not explain required parameters, default values, or the expected response format. For a creation tool, this lack of detail hinders an agent's ability to use it correctly without additional context.

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 100% of parameters with descriptions, so the baseline is 3. The description adds no parameter-level meaning beyond the schema; the dryRun mention is already in the schema. Thus, no additional value is provided.

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 purpose: 'Create a new Cloud DB for MSSQL instance.' The verb 'Create' and specific resource 'Cloud DB for MSSQL instance' make the action and target unambiguous. Although there are many sibling tools, the name and description distinguish it as MSSQL-specific.

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 like ncloud_create_mysql_instance or ncloud_create_postgresql_instance. There is no mention of prerequisites, required parameters, or context for selection. The only usage hint is dryRun, which is not a guideline for tool selection.

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