Power Off Server

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

Annotations already indicate destructiveHint=true, so the description's 'force power off' adds only the 'pulling the power cord' analogy. No additional behavioral context (e.g., data safety, prerequisites) is disclosed beyond annotations.

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?

Two short, direct sentences with no wasted words. The purpose is front-loaded and the analogy adds clarity efficiently.

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, destructive tool with one parameter and no output schema, the description is nearly complete. Minor gap: it does not mention prerequisites (e.g., server must be running) or the resulting state.

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 coverage is 100% for the single parameter 'id', which is described as 'Server ID' in the schema. The description does not add any extra meaning or context for this parameter.

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 ('force power off') and the resource ('a server'), with an analogy ('like pulling the power cord') that distinguishes it from graceful shutdown or reboot siblings.

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 immediate forceful shutdown but does not explicitly compare to alternatives like hetzner_shutdown or hetzner_reboot. No guidance on when to use this tool vs others is provided.

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