Restart PC

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

With no annotations, the description takes on the full burden of disclosing consequences. It clearly states that the server does NOT auto-start after reboot, that remote control will be lost until local interaction, and that confirm:true is required as a safety gate.

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?

Three sentences, front-loaded with the core action, and each sentence adds behavioral value. 'Requires confirm: true' is slightly redundant with the schema but is short and reinforces a critical safety requirement.

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 mutating, potentially disruptive tool with no annotations, the description covers the essential consequences and safety gate. It could more explicitly reference cancel_shutdown as an abort path, but the schema already covers that in delaySeconds.

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%: every parameter already has a meaningful description, including the delay range and the pointer to cancel_shutdown. The description only repeats the confirm requirement that is already in the schema, adding no new parameter-level meaning.

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?

States a specific action and resource: 'Schedule a restart of this machine.' It also distinguishes itself from shutdown_pc by explaining that remote control ends the same way after a restart until someone starts the machine locally.

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?

Gives clear context that this is a restart and warns about the post-reboot consequence that matches shutdown_pc. It does not explicitly say 'use shutdown_pc instead when...', but it gives enough framing for an agent to understand the operational trade-off.

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