ncloud_serverless_list_clusters

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

The readOnlyHint annotation already signals a safe read operation, and the description adds useful behavioral context: the default sort order and the fact that pageNo is 0-based. These details go beyond the schema and help the agent understand API behavior without contradicting 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 two sentences with no filler. The main action and resource are front-loaded, and each additional clause delivers necessary behavioral or parameter information.

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 read-only list operation with three optional parameters, the description combined with the fully documented schema covers all inputs needed to call the tool correctly. It does not describe the response shape, but there is no output schema and the purpose of a list operation is clear enough for an agent to proceed.

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 baseline is 3; the description adds extra value by enumerating the allowed sort fields ('name, createdDateTime') and the default ordering, which the schema only references generically as 'allowed fields per tool'. This meaningfully clarifies how to construct the sort parameter.

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 uses a specific verb ('List'), a precise resource ('Cloud DB Serverless (MySQL) clusters'), and the concrete API path (GET /mysql/v1/clusters). The resource qualifier clearly distinguishes this from sibling tools like ncloud_cdss_list_clusters and ncloud_ses_list_clusters.

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 clear usage context by naming the exact resource type and documenting the default sort behavior and page numbering semantics. It does not explicitly state when not to use this tool or name alternatives, but the resource-specific naming makes mis-selection unlikely.

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