set_keep_awake

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

With no annotations, the description carries the full burden but does add real behavioral context: the effect is transient and scoped to the active connection, and a WebSocket is mandatory. It still omits what happens on disconnect, whether the device retains any state, or what permissions/errors are involved.

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 front-loaded sentence with no filler; the core effect comes first and the prerequisite is appended compactly.

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 simple state-setting tool with no output schema, the description covers the effect and one prerequisite. It remains incomplete regarding the boolean's on/off semantics and the relationship to get_keep_awake_status, which an agent would need to invoke this correctly.

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 is one required parameter with 0% schema description coverage, so the description must explain it. It never mentions the 'enabled' boolean nor clarifies that passing false releases the keep-awake lock, so the schema parameter remains semantically opaque.

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 gives a specific verb+resource ('Prevents the screen from sleeping') and is clearly distinguishable from the sibling get_keep_awake_status. However, it only describes the enabling direction, while the required boolean parameter implies the tool can also turn keep-awake off, leaving that half of the purpose unstated.

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 discloses a precondition ('WebSocket required'), which is genuine usage context. But it never says when to call this versus get_keep_awake_status, nor when keep-awake should be set or unset, so the agent must infer the workflow.

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