sleep_calculator

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

With no annotations provided, the description carries the full burden. It adds a useful behavioral detail by revealing the 90-minute sleep-cycle basis for the calculation. However, it does not disclose output format, rounding behavior, or how invalid inputs are handled.

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?

Two concise sentences with no filler. The main purpose is front-loaded in the first sentence, and the second adds a meaningful algorithmic detail without redundancy.

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?

The tool has no output schema and no annotations, so the description should cover return values and input conventions. It explains the calculation concept but omits what the bedtime output looks like and the required wakeTime format, leaving an agent to guess or fail.

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 description coverage is 0%, so the description must compensate. It loosely maps 'wake time' to wakeTime and 'sleep goal' to sleepHours, but does not specify the expected string format for wakeTime or units/ranges for sleepHours. This leaves important parameter ambiguity.

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 a specific verb and resource: 'Calculate recommended bedtime from wake time and sleep goal.' It is distinct enough from the sibling sleep_debt_calculator by focusing on bedtime recommendation, though it does not explicitly name or differentiate from siblings.

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 intended use case is implied: when a user has a wake time and desired sleep duration, this tool computes a bedtime. However, there is no explicit guidance on when to prefer this over sleep_debt_calculator or other sleep-related tools, and no exclusions are stated.

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