Prevent Sleep

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

Annotations provide minimal behavior cues (not read-only, not destructive, not idempotent). The description mentions 'using caffeinate' but does not disclose important details such as whether it prevents display sleep or system sleep, whether it requires permissions, or what happens after the duration expires. More transparency is needed given sparse annotations.

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 that conveys the essential information without unnecessary words. It is front-loaded and efficient.

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 simplicity of the tool and that the schema and annotations are present, the description covers the basic purpose. However, it could be more complete by explaining what 'using caffeinate' entails (e.g., permissions, behavior when lid is closed). It is adequate but not thorough.

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 input schema fully documents the single parameter (seconds) with description, min, max, and default. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 tool prevents Mac from sleeping for a specified duration using caffeinate. It identifies the specific verb (prevent), resource (Mac sleep), and distinguishes from sibling tools like system_sleep (which puts Mac to sleep) and system_power (power management).

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 description describes what the tool does but does not explicitly state when to use it versus alternatives. While siblings like system_sleep suggest opposite actions, no direct guidance is given on when not to use this tool or which alternative to choose for other sleep-related tasks.

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