ncloud_list_mysql_backups

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

The readOnlyHint annotation already establishes the safe read-only nature, but the description adds no extra behavioral context such as pagination, response format, or scope limitations. It merely restates the action, contributing no insights beyond what annotations and the schema already provide.

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, concise sentence with no redundant words. It is perfectly front-loaded and every word contributes to understanding the tool's 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?

For a simple single-parameter list tool with readOnlyHint annotation, the description is adequate: it clearly states the action and resource. However, it does not mention the lack of backup details or the output structure (no output schema exists), leaving minor gaps for an agent that might confuse this with the sibling 'list_mysql_backup_details' 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?

The input schema has 100% coverage with one parameter ('cloudMysqlInstanceNo') described as 'Cloud MySQL instance number'. The description offers no additional parameter detail, but since the schema fully documents the parameter, the baseline score 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 'List backups for a Cloud DB for MySQL instance' uses a specific verb ('List') and resource ('backups for a Cloud DB for MySQL instance'). It clearly distinguishes from sibling tools like 'ncloud_list_mysql_backup_details' and 'ncloud_list_mysql_instances', making the tool's purpose 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 usage: call this when you need to list backups for a specific MySQL instance. However, it provides no explicit guidance on when to use this vs. closely related siblings (e.g., 'ncloud_list_mysql_backup_details') or any prerequisites/exclusions, leaving the agent to infer context from the tool name alone.

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