ncloud_create_mongodb_instance

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

Annotations only include destructiveHint:false, so the description carries the burden of behavioral disclosure. It adds the dryRun preview behavior, which is helpful. However, it doesn't disclose that creating an instance incurs costs, may be a long-running operation, or requires specific permissions. These are significant behavioral traits for a creation tool.

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 exactly two short sentences, front-loaded with the action 'Create a new Cloud DB for MongoDB instance' and followed by a concise dryRun tip. There is zero wasted wording, and the structure is immediately scannable.

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?

This is a high-complexity tool with 25 parameters, 7 required, and no output schema. The description is only two sentences and doesn't explain how parameters interact (e.g., clusterTypeCode determines which product codes and shard counts are needed). It also doesn't mention what a successful creation returns or any prerequisites like VPC/subnet setup. The schema descriptions help, but the description itself is insufficient for the tool's complexity.

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% with descriptions for all 25 parameters, so the baseline is 3. The description's mention of dryRun adds no new semantic value since the schema already documents dryRun with a default of false. No additional parameter relationships or conditional logic are explained.

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 the specific verb 'Create' and identifies the resource as 'Cloud DB for MongoDB instance,' clearly distinguishing it from sibling tools like list_mongodb_instances, delete_mongodb_instance, and get_mongodb_instance_detail. The dryRun option is also surfaced, reinforcing the creation intent.

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 a useful usage hint for dryRun=true as a preview mode without creating. However, it doesn't explicitly state when to use this tool versus alternatives for managing existing instances or performing other MongoDB operations. Usage is implied by 'Create' but lacks explicit exclusions or alternative references.

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