ncloud_list_mysql_logs

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

The annotations already declare readOnlyHint: true, indicating safe read behavior. The description does not add any additional behavioral context such as pagination, rate limits, or response format. With annotations covering the safety profile, a score of 3 is appropriate as the description adds minimal extra value.

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 sentence of 9 words, front-loaded with the key action and resource. It is efficient and contains no unnecessary words or redundancy.

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 list operation with no output schema, the description adequately conveys the purpose. It could mention that it returns log file names or details, but it is sufficiently complete. Given the lack of output schema and sibling tools with similar patterns, a score of 4 is reasonable.

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 descriptions for both regionCode and cloudMysqlServerInstanceNo. The description does not add any meaning beyond what the schema already provides. Baseline 3 is suitable since the schema carries the burden.

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 'List DB server log files for a Cloud DB for MySQL server instance', specifying the action (list) and resource (log files for a MySQL instance). It distinguishes from sibling tools like ncloud_export_mysql_log by using the verb 'list', but does not explicitly differentiate from other list tools such as ncloud_list_mysql_backups or ncloud_list_postgresql_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 provides no guidance on when to use this tool versus alternatives. For example, it does not indicate that this is a read-only operation (covered by annotations) or suggest using ncloud_export_mysql_log for downloading logs. The agent is left to infer usage from the tool name and context.

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