ncloud_list_mysql_databases

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

The description is consistent with the readOnlyHint=true annotation, indicating a safe read operation. However, it does not add any behavioral details beyond the annotation, such as pagination, result format, or limitations. The annotation already covers the safety profile, so a score of 3 is appropriate.

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 very concise at one sentence, with no wasted words. However, it could be slightly more informative without becoming verbose (e.g., mention that it returns a list of database names).

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-only list tool with one parameter, the description is adequate but not fully complete. It does not mention the output format or any constraints. Given the annotations and simplicity, a score of 3 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 a clear description for the single parameter. The tool description adds no further meaning to the parameter beyond what the schema provides, so baseline 3 is correct.

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 resource 'databases', and clarifies the scope 'in a Cloud DB for MySQL instance'. It clearly distinguishes this tool from sibling tools like ncloud_list_mysql_users and ncloud_list_mysql_instances.

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 does not provide any guidance on when to use this tool versus alternatives (e.g., ncloud_list_mysql_instances, ncloud_add_mysql_databases). It lacks context such as prerequisites (need an instance) or sequencing (list before add/delete).

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