projector_sleep

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

Annotations already declare this is not read-only, not destructive, and closed-world, so the agent knows it changes state safely. The description adds that the action turns off the display, but it does not mention how the screen is woken (e.g., projector_wake) or whether this affects projector state beyond display output. With annotations carrying the safety profile, this is adequate but not rich.

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?

One short sentence with the key operation front-loaded and a clarifying parenthetical. No wasted text.

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 action, the description is nearly complete. It could improve by mentioning the counterpart wake tool or any state implications, but nothing critical is missing for invocation.

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?

There are zero parameters, so the baseline is 4. The description does not need to explain parameter meaning, and no parameter details are missing.

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 ('Put to sleep') and resource ('projector screen'), with a parenthetical clarifying that this means turning off the display. It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools like projector_wake or set_monitor_dpms.

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?

Usage is implied by the word 'sleep' and the parenthetical, but there is no explicit statement of when to use this instead of related tools such as projector_wake or disable_monitor. The context is clear enough for a simple action, but alternatives are not named.

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