ncloud_create_mssql_slave

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

No annotations beyond destructiveHint=false. The description confirms creation is non-destructive but provides no additional behavioral context (e.g., replication behavior, impact on primary instance). Meets minimum 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?

Single sentence, 12 words, front-loaded with the verb 'Create'. No wasted words 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 creation tool with no output schema, the description should hint at return values or side effects (e.g., 'returns slave instance details'). It only states the action, leaving agents unaware of the response format or follow-up steps.

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 coverage is 100%, so the schema already documents all parameters. The description does not add meaning beyond the schema (e.g., explaining why privateDomainPostfix is needed or subnetNo usage). Baseline 3 is appropriate.

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 action ('create') and the specific resource ('slave server instance for a Cloud DB for MSSQL instance'). It distinguishes itself from sibling tools like ncloud_create_mysql_slave by specifying MSSQL.

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?

No guidance on when to use this tool versus alternatives (e.g., when to create a slave vs. other operations). Does not mention prerequisites or contexts where creation is appropriate.

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