ncloud_create_mysql_recovery

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

Annotations only provide destructiveHint: false, which is consistent with 'Create'. The description adds no further behavioral context like expected duration, permissions needed, cost implications, or that the recovery server is a separate instance that may require management. It does not contradict annotations.

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, no redundant information, and front-loaded with the core purpose. Every phrase serves a purpose.

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?

As a creation tool with no output schema, the description lacks context about return values, expected behavior (e.g., server provisioning time), and prerequisites such as the existence of a Cloud MySQL instance. Minimal additional guidance is provided beyond the basic action.

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?

All six parameters are fully described in the input schema (100% coverage). The description mentions the two restore methods (file vs point-in-time) which aligns with fileName and recoveryTime, but adds no additional semantic value beyond the schema's parameter descriptions.

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 a Recovery server instance) and the resource (Cloud DB for MySQL instance). It also specifies two restore methods (backup file or point-in-time). Among sibling tools, this is distinct but could be more explicit about its unique role compared to other MySQL recovery-related tools.

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 a purpose (recovery) but provides no explicit guidance on when to use this tool versus alternatives like ncloud_list_mysql_backups or ncloud_get_mysql_recovery_time. It lacks when-not-to-use scenarios or prerequisites, such as requiring an existing Cloud MySQL instance.

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