ncloud_reboot_mongodb_server

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

Annotations indicate idempotentHint:true and destructiveHint:false, but the description adds no behavioral context (e.g., downtime, impact on clients, required permissions). The brief description fails to reveal key traits beyond what annotations already convey.

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?

A single, precise sentence with no unnecessary words. Efficiently communicates the core purpose.

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 straightforward reboot operation with one parameter and no output schema, the description is minimally adequate. However, it lacks context on downtime or operational impact, which could be helpful.

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?

The single parameter 'cloudMongoDbServerInstanceNo' is already fully described in the schema with coverage 100%. The tool description adds no additional semantics.

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 action 'Reboot' and the target resource 'Cloud DB for MongoDB server instance'. It distinguishes from sibling tools like ncloud_reboot_server or ncloud_reboot_mysql_server by specifying MongoDB.

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?

No guidance on when to use this tool versus alternatives like ncloud_reboot_mysql_server. No prerequisites, when-not conditions, or context for rebooting a MongoDB instance.

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