ncloud_list_mysql_backup_details

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

The annotation readOnlyHint=true already covers the safety profile. The description adds that file names are included in the response, which is useful context, but does not disclose other behavioral traits such as pagination, ordering, or any potential limitations. With annotations present, this is acceptable but not exceptional.

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, clear sentence that conveys the core purpose and a key feature (file names) without any redundant wording. It is front-loaded and easy to parse.

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 low complexity (2 flat parameters, no output schema), the description is fairly complete. It explains what the tool returns (detailed backup information including file names) and identifies the target resource. The absence of an output schema is partly mitigated by this description, though more specific return-field details could improve completeness.

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?

Both parameters are fully described in the schema (100% coverage), so the baseline is 3. The description itself adds no parameter-level detail beyond signaling that the operation is tied to a specific MySQL instance, which is already evident from the schema's cloudMysqlInstanceNo parameter.

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 ('List') and clearly identifies the resource ('detailed backup information ... for a Cloud DB for MySQL instance'), including a distinguishing detail ('including file names'). It effectively separates this from sibling tools like ncloud_list_mysql_backups or ncloud_get_mysql_instance_detail.

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 phrase 'detailed backup information' implies that this is for more granular data than a simple backup list, but there is no explicit guidance on when to choose this over ncloud_list_mysql_backups or other related tools. Usage context is implied rather than stated.

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