ncloud_upgrade_mysql_version

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

With empty annotations, the description should disclose behavioral traits like potential downtime, connection impact, or whether the operation is asynchronous. It only states 'upgrade', implying a mutation, but no details on side effects. This is insufficient for a mutation tool.

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 (11 words) that is front-loaded with the action and resource. Every word adds value, no fluff.

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 mutation tool with 5 parameters and no annotations or output schema, the description is too minimal. It lacks context on the upgrade process, prerequisites, and post-operation effects, leaving the agent with gaps.

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 the input schema provides descriptions for all parameters. The tool description adds no additional meaning beyond what is already stated. Baseline score of 3 is appropriate.

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 'Upgrade the DB engine version of a Cloud DB for MySQL instance' clearly states the action (upgrade) and the resource (DB engine version of a MySQL instance). It is specific enough to differentiate from sibling tools like 'reboot' or 'change spec', but does not mention the distinction between major and minor upgrades, which the input schema reveals.

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, prerequisites (e.g., needing an instance number and image product code), or alternatives. Sibling tools like 'get_mysql_image_products' are used to obtain parameters for this tool, but no such relationship is indicated.

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