ncloud_serverless_create_cluster

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

Annotations only declare destructiveHint=false, so the description carries most of the behavioral disclosure. It reveals that the call is asynchronous (202 Operation), that without autoScale the cluster is pinned to unit.max, and that dryRun masks the password. These are non-obvious traits beyond what the schema conveys.

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?

Three short sentences, each adding distinct value: core purpose with endpoint, a behavioral caveat about autoScale, and a pointer to the version source plus dryRun option. No filler or redundant restatement of the schema.

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 tool with 11 parameters and 8 required nested objects, the description offers the most important cross-cutting context (async behavior, engineVersion sourcing, dryRun, pinning). The schema covers the mandatory fields thoroughly, and with no output schema, the 202 reference is an acceptable hint about the asynchronous result. A note on how to poll the operation would make it complete, but this is a minor gap.

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 55%, so the description has room to compensate but only partially does. It clarifies that unit.max acts as a pin when autoScale is off and that engineVersion should come from a specific sibling tool. Most parameter semantics remain in the schema, which already documents unit, autoScale, backupConfig, and initialDatabase in detail.

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 verb ('Create') and resource ('Cloud DB Serverless (MySQL) cluster'), and adds the API endpoint and operation code. It distinguishes this from the many sibling cluster-creation tools (SES, CDSS, Hadoop) by naming the specific service and resource type.

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 on when to use the tool: to create a Serverless MySQL cluster. It also provides actionable usage guidance by pointing to ncloud_serverless_list_engine_versions for engineVersion and recommending dryRun=true for preview. It doesn't explicitly name alternative tools or exclusions, but the resource type and cross-references are sufficient for selection.

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