ncloud_get_mysql_products

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

The description is consistent with the readOnlyHint annotation, indicating a read-only listing operation. However, it adds no further behavioral context beyond what the annotation provides. For a simple read tool, this is adequate but not enhanced.

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 that is clear and to the point. Every word is useful with no filler or repetition. It is appropriately sized for the tool's simple functionality.

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 simple nature of the tool (a listing operation), the description is nearly complete. It covers the purpose and the required dependency (image product code). However, it could mention that the output product codes are used for selecting server specs when creating a MySQL instance, but this is not essential.

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 coverage is 100%, so both parameters have descriptions in the schema. The tool description adds no additional semantic value beyond restating that the required parameter is an image product code. The description is redundant with the schema descriptions.

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 the tool lists Cloud DB for MySQL server spec product codes for a given image product code. It uses a specific verb ('List') and identifies the resource ('Cloud DB for MySQL server spec product codes'). It implicitly distinguishes from sibling tools like ncloud_get_mysql_image_products, which lists image product codes.

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 that one must first obtain an image product code from another tool (e.g., ncloud_get_mysql_image_products), but it does not explicitly state this dependency or provide any when-to-use or when-not-to-use guidance. No alternatives are mentioned, so the guidance is minimal.

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