start_sleep_prevention

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

With no annotations, the description must compensate but only states 'preventing system sleep'. It does not explain behavioral details like whether modes affect different sleep states, the effect of indefinite duration, or what happens if sleep prevention is already active.

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 a single sentence with no redundant words. However, it could leverage the space to include more useful details without becoming lengthy.

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?

Given the absence of an output schema and the presence of sibling tools, the description fails to explain return values, side effects, or how this tool interacts with others (e.g., 'stop_sleep_prevention'). It is insufficient for an agent to understand the tool's full context.

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?

Schema coverage is 100%, so the schema already describes both parameters. The description adds no new meaning beyond 'specified mode and duration', which merely restates the schema.

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 action (start preventing system sleep) and mentions the parameters (mode and duration). It implicitly differentiates from sibling 'stop_sleep_prevention' by verb, but does not explicitly address other siblings like 'set_duration_preset'.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'set_duration_preset'). There is no mention of prerequisites, typical use cases, or when not to use it.

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