ncloud_create_mssql_instance

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

The annotation destructiveHint=false is consistent with a create operation. The description adds the dryRun behavior, which is useful, but it does not disclose whether the operation is synchronous, what happens on success, or potential cost implications.

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 two concise sentences with no wasted words. It front-loads the primary purpose and adds a single actionable tip about dryRun.

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?

This is a complex tool with 20 parameters, no output schema, and only a minimal annotation. The description does not mention return values, required setup steps, or how to choose among the many parameters. It relies entirely on the schema for context, which is insufficient for a creation tool of this complexity.

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 schema already explains all parameters. The description adds no parameter-specific detail beyond repeating the dryRun flag's schema description, which provides minimal additional value.

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 states 'Create a new Cloud DB for MSSQL instance' with a specific verb and resource. It clearly indicates the tool creates an MSSQL instance, distinguishing it from related sibling tools like create_mssql_slave or list_mssql_instances.

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 only mentions a dryRun flag but does not explain prerequisites, when to prefer creating a slave, or when to query existing instances first.

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