Restart graphics driver

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

With no annotations provided, the description carries full responsibility for behavioral transparency. It discloses that the tool sends a built-in Windows hotkey, that the driver reinitializes, and that the screen will flicker or go black briefly as an expected side effect. It also reassures that apps and work are preserved.

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 concise and front-loaded, stating the main benefit first, then the mechanism, then when to call it, then the expected side effect. Every sentence carries necessary information and no filler is present.

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 zero-parameter, no-output-schema tool, the description covers the essential context: what problem it solves, how it solves it, when to use it, and what side effects to expect. The agent has enough information to invoke it appropriately.

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 input schema has zero parameters, so there is no parameter semantics to add, earning the baseline of 4. The description's focus on the action and effect is appropriate because there is nothing to configure.

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 fixes frozen, stuck, black, or glitched screens via a graphics driver restart, and specifies the exact mechanism (Ctrl+Shift+Win+B). It is easily distinguished from sibling tools like restart_pc or open_app because it targets graphics resets specifically.

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 gives explicit usage guidance: call this whenever the user reports a frozen, stuck, unresponsive, or visually glitching screen and a graphics reset is a reasonable first step. It does not mention exclusions or alternatives, so it stops short of a 5, but the context is clear.

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