ncloud_hadoop_test_hive_metastore

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

The annotation readOnlyHint: true already discloses that this is a safe read operation, and the description's 'Test connectivity' aligns with that. However, the description adds no extra behavioral context beyond the annotation—such as whether the test is synchronous, what success/failure looks like, or that it sends credentials to the target. With annotations present, the bar is lower, but the description adds minimal value beyond the annotation.

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 is front-loaded with the verb 'Test' and clearly identifies the resource. No unnecessary words or repetition. It is appropriately sized for its purpose.

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?

The tool has a fairly simple purpose, and the schema and annotations cover parameter details and the read-only nature. However, there is no output schema and the description does not explain what the test result will look like (e.g., return values, error cases) or when a user would typically invoke this tool (e.g., before configuring a metastore). This is minimally adequate for a simple test tool but leaves some gaps in operational context.

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 description coverage is 100%, so all six parameters have descriptions. The tool description adds the high-level context that this is for an external Hive metastore backed by Cloud DB for MySQL, but it does not provide any parameter-specific clarifications or explain how the parameters relate to the connectivity test. This matches the baseline of 3 where the schema does the heavy lifting.

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 ('Test connectivity') and the specific resource ('external Hive metastore (Cloud DB for MySQL)'). This distinguishes it from sibling tools like ncloud_hadoop_save_hive_metastore, which is about saving configuration rather than testing.

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 gives no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or that it might be a precursor to saving metastore settings. The context implied by the name is not expanded in the description.

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