ncloud_reboot_cache_server

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

Annotations indicate idempotent and non-destructive behavior, which aligns with the 'Reboot' action. The description adds no further behavioral context beyond this. With annotations covering safety, a score of 3 is appropriate as the description does not elaborate on effects like temporary downtime or state changes.

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, clear sentence with no extraneous words. It is front-loaded and directly conveys the tool's purpose. Every word earns its place, making it highly efficient for a simple one-parameter tool.

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 simple reboot tool with a single required parameter and no output schema, the description is minimally adequate. It states the action and resource, but does not mention return values, confirmation, or edge cases. Given the low complexity and the presence of annotations, this is acceptable but not thorough.

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 sole parameter, 'cloudCacheServerInstanceNo', is fully described in the schema ('Cloud Cache server instance number to reboot'). The description adds no additional meaning beyond what the schema already provides. Schema coverage is 100%, so baseline score of 3 applies.

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 Cache server instance'), which is precise and distinguishes this tool from sibling reboot tools for other services like MySQL or PostgreSQL. The verb+resource combination is specific and unambiguous.

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. While the name implies it is for cache servers, there is no explicit mention of context, prerequisites, or when not to use it. Siblings include multiple reboot tools, but no comparative information is given.

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