ncloud_serverless_get_instance

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

Annotations already provide readOnlyHint=true, which covers the safety profile, and the description aligns with that by describing a GET operation. The description adds the HTTP endpoint context but does not go further, e.g., no mention of error cases or what the returned instance object contains.

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?

A single front-loaded sentence that states the action, resource, and HTTP endpoint with zero wasted words. The endpoint adds practical value without bloating the description.

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 two-parameter read operation, the schema documents both parameters fully and the annotation covers read-only safety. The only minor gap is that the return payload is not described, but with no output schema and low complexity, this is a small omission.

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% and both parameters (clusterName, instanceName) already have descriptive text plus validation patterns. The description adds no parameter-level meaning beyond what the schema provides, so the baseline score of 3 applies.

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 verb ('Get') plus a precise resource ('one instance of a Cloud DB Serverless cluster') and includes the exact HTTP endpoint. The singular 'one instance' clearly distinguishes this from sibling list tools like ncloud_serverless_list_instances.

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?

There is no guidance about when to use this tool versus alternatives such as ncloud_serverless_list_instances or ncloud_serverless_get_cluster. The usage is merely implied by the name and description, with no exclusions or selection conditions stated.

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