ncloud_reboot_mysql_server

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

With annotations already indicating idempotency and non-destructive nature, the description adds no further behavioral context such as expected downtime or connection impact. It simply restates the action.

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, concise sentence that gets straight to the point with no wasted words.

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?

Given the simple nature of the tool, full parameter schema, and annotations covering safety, the description is adequate for selection and invocation. However, it lacks any additional context about side effects, but that is not critical for a straightforward reboot operation.

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 schema already fully documents the single parameter (cloudMysqlServerInstanceNo) with a description, and the tool description does not add additional semantics. Baseline 3 applies for full schema coverage.

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 'Reboot' and identifies the resource as 'Cloud DB for MySQL server instance', clearly distinguishing it from sibling reboot tools for other database types (e.g., PostgreSQL, 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?

The description provides no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. It is a bare statement of the operation.

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