ncloud_list_mysql_logs

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

The readOnlyHint annotation already declares the safe read-only nature. The description adds the detail that it lists 'log files' (not log content), which is a mild behavioral note. However, it does not explain pagination, ordering, or what fields are returned. With annotations covering safety, the description adds some but not extensive behavioral context.

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 that is front-loaded with the core action and resource. It contains no redundant words or filler, efficiently stating 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?

This is a simple list operation with 2 parameters and no output schema. The description covers the essential scope (listing DB server log files for a specific MySQL instance). It would benefit from mentioning the return format or the types of log files available, but given the simplicity and existing schema/annotations, it is reasonably complete.

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% for both parameters (regionCode and cloudMysqlServerInstanceNo), with descriptions in the schema. The tool description does not add any parameter-specific meaning or clarify usage beyond the schema. Baseline 3 is appropriate since the schema already documents parameter semantics.

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 specifies the exact action ('List'), the resource type ('DB server log files'), and the target service ('Cloud DB for MySQL server instance'). This is a specific verb+resource combination that clearly distinguishes it from siblings like ncloud_export_mysql_log (which exports logs rather than listing) and ncloud_list_mysql_backups (which lists backups, not logs).

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 conveys that the tool is for listing log files on a specific MySQL instance but does not provide explicit when-to-use guidance or mention alternatives. It does not state when to prefer this over ncloud_export_mysql_log or clarify that it lists files without downloading contents. The context is enough for basic usage but lacks explicit exclusions or alternative recommendations.

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