ncloud_get_mysql_recovery_time

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

With readOnlyHint=true provided by annotations, the description adds value by disclosing that the tool returns a time range (recoveryStartTime ~ recoveryEndTime). It does not describe edge cases, permissions, or rate limits, but for a simple read operation, the description sufficiently covers what the tool does and returns.

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, 16-word sentence that immediately communicates the tool's purpose and output. No redundant or filler content, and the most important information (the data returned) is front-loaded.

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 read tool with two well-documented parameters and no output schema, the description clearly states what is returned (a time range). It does not specify the exact format of the range (e.g., timestamps), but this is likely implied and acceptable for the tool's simplicity.

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% for the two parameters (regionCode and cloudMysqlInstanceNo), each with basic descriptions. The tool description does not add additional semantic detail about the parameters themselves, 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 uses a specific verb ('Get') and names the exact resource ('available recovery time range for a Cloud DB for MySQL instance'). It clearly distinguishes this tool from sibling tools like ncloud_create_mysql_recovery and ncloud_get_mysql_instance_detail by specifying the time range output.

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 clear context: it is for retrieving the recovery time range for a MySQL instance. It does not explicitly mention alternatives or exclusions, but the purpose is specific enough that an agent would know when to use it. No when-not-to-use guidance exists, but this is a straightforward getter.

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