cloud_power_off_server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions that it does not gracefully shutdown, omitting potential consequences like data loss, forced stop implications, or required permissions for a destructive 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 sentence with zero wasted words. It efficiently conveys the core functionality and key differentiator (hard vs graceful). Front-loaded with the action.

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 tool is destructive and has no annotations, the description is incomplete. It does not mention prerequisites (e.g., server must exist and be powered on), potential data loss, or any side effects. The output schema exists but the description fails to provide essential context for a forceful 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?

Schema description coverage is 0%, so the description must add meaning to parameters. However, it only names the server_id parameter without providing any additional context about its format, source, or role beyond what the schema already indicates (an integer).

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 tool performs a hard power-off on a cloud server, contrasting with graceful shutdown. It uses a specific verb ('Hard power-off') and resource ('cloud server'), distinguishing it clearly from sibling tools like cloud_shutdown_server.

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 implies usage for non-graceful power-off but does not explicitly state when to use this tool versus alternatives like cloud_reboot_server or cloud_shutdown_server. No when-not-to-use or prerequisites are mentioned.

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