monitor_off

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

Annotations already indicate this is a mutating, non-destructive, open-world action. The description adds the exact effect (blanking the display) but does not clarify edge cases such as what happens if the display is already off, or whether it affects system sleep state. This is acceptable given the simplicity, but not rich in behavioral disclosure.

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 sentences with the core action first and usage trigger phrases second. Every word earns its place; there is no redundancy or fluff.

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 parameterless, no-output tool, the description fully explains what it does and when to invoke it. An agent can correctly call this tool without additional context, especially given the straightforward nature of the action.

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 tool has zero parameters, so the schema already fully covers the input space. The description does not need to add parameter details; the baseline of 4 for 0-parameter tools applies here.

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 states a specific verb and resource: 'Turn the monitor/screen off (blank the display)'. It clearly distinguishes from siblings like monitor_on, lock_screen_display, and set_display_brightness by focusing on the exact action of blanking the display.

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 says to use when the user says 'turn off the screen', 'blank the display', or similar, giving clear triggering language. It does not name alternatives like monitor_on or lock_screen_display, but the guidance is still unambiguous and actionable.

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