Power Off Server

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

The description adds the hard-shutdown nature and compares it to 'pulling the power cord', effectively conveying the abrupt, potentially destructive behavior beyond the destructiveHint annotation. No contradiction with 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 concise sentences with the core action first and the advisory alternative second. No filler or redundant information.

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 single-parameter action with clear annotations, the description covers purpose, usage, and behavioral caveats sufficiently. No output schema is needed for this simple 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 fully describes the only parameter (id) with description and exclusiveMinimum, achieving 100% schema coverage. The tool description adds no additional parameter context, so the baseline 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 'Power off a server (hard shutdown)', using a specific verb and resource while distinguishing it from graceful shutdown and sibling tools like reboot or power-on.

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?

It explicitly provides an alternative: 'For a graceful shutdown, SSH into the server and run shutdown.' This tells the agent when not to use this tool and clarifies it is for abrupt hard shutdowns.

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