ncloud_hadoop_list_mysql_instances

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

The description is consistent with the readOnlyHint annotation, which already signals a safe read operation. It adds some scoping context ('for Hive metastore integration') but does not disclose details like filtering behavior, pagination, or response format. This is similar to the high-calibration example where limited extra context earned a 3.

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 that leads with the verb and resource, with no redundant content. Every word adds value, making it highly efficient for an agent to parse.

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?

While the tool is simple (2 params, read-only, no output schema), the description lacks critical contextual details: it does not explain how parameters filter results, what the returned list contains, or how this relates to Hive metastore setup. The ambiguous phrase 'for Hive metastore integration' could mean these instances are already integrated or are candidates, creating confusion. This is insufficient for an agent to reliably select and invoke the tool.

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 fully describes both parameters ('Region code' and 'Cloud Hadoop instance number') with 100% coverage, so the baseline is 3. The description does not add any additional meaning about how these parameters affect the listing, nor does it clarify the role of 'cloudHadoopInstanceNo' in the Hadoop context.

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 action ('List') and the resource ('Cloud DB for MySQL instances') with a specific purpose ('for Hive metastore integration'). This distinguishes it from the sibling tool 'ncloud_list_mysql_instances' (generic MySQL listing) and other Hadoop-related tools.

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 phrase 'for Hive metastore integration' implies when this tool is useful, but it does not explicitly mention alternatives or exclusions. There is no guidance on when to prefer this over 'ncloud_list_mysql_instances' or other similar tools, leaving usage context implied rather than explicit.

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