projector_wake

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

Annotations already declare this is a mutating but non-destructive, non-open-world operation, so the safety profile is covered. The description adds only that the effect is turning on the display; it does not say whether the call is idempotent when already awake, how long wake takes, or what happens if the projector is unreachable.

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?

A single sentence with a parenthetical that adds real disambiguation rather than redundancy. No wasted words, and the action is 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?

For a zero-param, single-effect tool with no output schema, the description covers what the agent needs, but it omits the state/failure behavior an agent would want before invoking a hardware 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 schema takes zero parameters, which is the baseline-4 case; there is nothing for the description to add or omit.

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 verb (wake) and resource (projector screen) plus a clarifying gloss '(turn on display)', which disambiguates from set brightness or fullscreen siblings. It doesn't explicitly reference the complementary projector_sleep, so it falls short of 5.

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 name and description imply when to use it (to turn the display on), and the sibling set contains projector_sleep which makes the inverse obvious, but the description itself names no alternatives, prerequisites, or conditions.

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