ncloud_create_mysql_slave

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

Annotations only provide `destructiveHint: false`, indicating non-destructive operation. The description calls it a 'read replica', adding basic behavioral context, but fails to disclose traits like potential asynchronicity, required instance state, or multi-zone dependencies (noted in schema but not description). With minimal annotation support, the description should provide more behavioral insight.

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 sentence that directly states the action and resource with no extraneous words. It is front-loaded and efficient, earning maximum conciseness points.

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 (creating a read replica), the description is minimally adequate. It does not cover expected outcomes (e.g., replication, read scaling) or prerequisites beyond what the schema hints. The missing output schema increases reliance on description for completeness, but it falls short of full 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?

Schema description coverage is 100%, so all parameters are already explained. The tool description does not add extra meaning beyond 'slave (read replica)', which is already implied. Per guidelines, high coverage allows baseline 3; no additional semantic 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 verb 'Create' and the resource 'slave (read replica) for a Cloud DB for MySQL instance'. It distinguishes this tool from siblings like `ncloud_create_mysql_instance` (creates main instance) and `ncloud_create_mssql_slave` (for MSSQL). The purpose is specific and unambiguous.

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 use for creating a read replica, but offers no explicit guidance on when to use vs. alternatives (e.g., `ncloud_create_mysql_recovery`) or when not to use. It lacks prerequisites or caveats. While the purpose is clear, the absence of usage boundaries or exclusions makes it merely adequate.

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