ncloud_serverless_list_databases

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

The readOnlyHint annotation already covers the safety profile, and the description adds useful behavioral context: the operation targets databases of a specific cluster and returns up to 1,000 databases. It does not go into pagination behavior, but the schema already documents pagination parameters, so the added value is reasonable.

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 sentence containing only essential facts: the action, the resource scope, the API path, and the result cap. There is no filler or repetition of schema content.

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 read-only list operation with a fully described input schema, the description is nearly sufficient for selection and invocation. It could be slightly stronger by naming sortable fields or noting the output item shape, especially since there is no output schema, but those are minor 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 description coverage is 100%, so all four parameters are already documented with type, constraints, and defaults. The description adds no parameter-specific meaning beyond placing clusterName in the endpoint. A baseline of 3 is appropriate when the schema carries the full load.

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 and resource: 'List databases of a Cloud DB Serverless cluster,' and reinforces it with the exact REST endpoint. This clearly distinguishes it from sibling listing tools like serverless_list_clusters or serverless_get_database.

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 clear context: this is the per-cluster database listing operation, and it notes a scale limit. However, it does not explicitly contrast with alternatives such as serverless_get_database or the create/delete database tools, so the usage guidance is implied rather than stated.

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