ncloud_reboot_mongodb_server

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

The annotations already declare idempotentHint=true and destructiveHint=false, leaving a low burden on the description. However, the description provides no additional behavioral traits beyond the annotations—nothing about temporary downtime, asynchronous execution, or instance-state requirements. It does not contradict the annotations, but it is essentially silent on behavior.

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, front-loaded with the action verb, and contains zero filler words. Every word earns its place by precisely stating the tool's purpose. It is appropriately sized for a simple one-parameter reboot operation.

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?

The tool is low-complexity (one required parameter, no output schema) and the annotations cover the safety profile, so the description is minimally sufficient. However, it lacks operational context that would help an agent set expectations, such as the instance becoming temporarily unavailable or the reboot being asynchronous.

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 cloudMongoDbServerInstanceNo already described as 'Cloud MongoDB server instance number to reboot'. Therefore the baseline is 3. The description adds no additional parameter meaning beyond the schema; the single parameter's semantics are fully captured by the schema.

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 'Reboot a Cloud DB for MongoDB server instance' uses the specific verb 'Reboot' and clearly identifies the target resource (Cloud DB for MongoDB server instance). It distinguishes from sibling reboot tools like ncloud_reboot_mysql_server by naming MongoDB, though it is essentially a short paraphrase of the tool name without explicit differentiation from alternatives.

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 on when to use this tool, what prerequisites exist, or which alternatives apply. It does not mention that the instance must be running, that the instance number can be obtained from ncloud_list_mongodb_instances, or that other reboot tools (e.g., ncloud_reboot_mysql_server) should be used for other database types. Usage is only implied by the name.

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