ncloud_get_mysql_products

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

The description is consistent with the readOnlyHint=true annotation but adds no extra behavioral context beyond what annotations already provide. It does not mention pagination, output format, or any side effects. With annotations covering the read-only nature, the description adds some value by specifying the input dependency but lacks richer behavioral disclosure.

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, direct sentence that front-loads the action and resource. There is no wasted information, and it conveys the essential purpose efficiently.

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 operation with thorough parameter descriptions and a readOnlyHint annotation, the description is adequate. It could optionally clarify the return value format, but 'List' strongly implies a list of codes, and the schema already specifies the input dependency. Overall, it is complete for the tool's complexity.

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%, with both parameters described in detail. The description directly references the required parameter ('image product code'), aligning with the schema's cloudMysqlImageProductCode. However, it does not add meaningful syntax or semantic details beyond what the schema already states.

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 states a specific action ('List') and a specific resource ('Cloud DB for MySQL server spec product codes') with a clear scope ('for a given image product code'). It distinguishes this tool from sibling tools like ncloud_get_mysql_image_products and ncloud_get_postgresql_products by explicitly naming the MySQL server spec product code context.

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 usage in a workflow where an image product code is already known, but it does not explicitly state when to use this tool versus alternatives. No alternative tools are named, and no when-not-to-use guidance is provided. The prerequisite relationship is only hinted at by the phrase 'for a given image product code'.

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