ncloud_create_mysql_slave

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

Annotations only include destructiveHint=false, and the description adds the read-replica context. However, it does not disclose behavioral aspects like provisioning time, billing implications, or that this is a write operation (the annotation already covers non-destructiveness). No contradiction found.

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 containing only the essential purpose. No filler or redundant information; every word contributes to the meaning.

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 simple create operation with three fully described parameters and no output schema, the description adequately conveys the tool's function. It clarifies the ambiguity of 'slave' with the parenthetical 'read replica'. Minor gaps remain about the operation's workflow or response, but these are not critical for this low-complexity tool.

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%, and the schema already provides clear descriptions for each parameter (e.g., subnetNo conditions). The tool description adds no additional parameter meaning beyond what the schema states, so the baseline of 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 a specific action on a specific resource: 'Create a slave (read replica) for a Cloud DB for MySQL instance'. The verb 'Create' and resource 'slave for MySQL instance' distinguish this from sibling tools like ncloud_create_postgresql_read_replica and ncloud_create_mssql_slave.

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 usage when a MySQL read replica is needed, but does not explicitly state when to use this over alternatives or mention prerequisites. There is no 'when not to use' guidance, leaving the agent to infer context from the resource type.

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