computer_restart

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

No annotations are provided, so the description carries the transparency burden. It proactively discloses that the operation does not erase the writable filesystem, which is a key behavioral guarantee. It does not mention other behavioral aspects like graceful vs. forced restart, but for this simple operation, the main concern (data loss) is addressed.

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, concise sentence that immediately states the action and the key qualifier. It has zero fluff and is perfectly front-loaded.

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 low complexity (1 parameter, no annotations, no output schema), the description sufficiently covers the tool's purpose and the most important behavioral characteristic (non-destructive restart). It could have elaborated on prerequisites or effects on running processes, but the provided information is adequate for a simple restart tool.

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 provides 100% coverage for the single parameter 'computer_id' with a clear description ('Computer slug to restart'). The tool description adds no additional parameter context, so a baseline score of 3 is appropriate per the schema coverage guideline.

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 uses a specific verb ('Restart') and resource ('computer'), and explicitly distinguishes from the sibling 'computer_factory_reset' by stating 'without erasing its writable filesystem'. This makes the tool's purpose clear and differentiates it from similar operations.

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 clear context that this tool is for restarting while preserving the filesystem, which implies it should be used over factory reset when data retention is desired. However, it doesn't explicitly name alternatives or state when not to use it, so it just misses a top score.

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