calculate_sleep_cycles

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

The description mentions it estimates based on 90-min cycles and returns 4-6 recommendations, but it contradicts the schema by suggesting only one input is needed (target wake or bedtime) while the schema requires both parameters. No annotations are provided, so the description carries the full burden but has a clear discrepancy.

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 two sentences plus a reference to list_bundles, front-loading the purpose and key behavior. Every sentence adds value with no waste.

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 tool's simplicity and 100% schema coverage, the description provides the core cycle-based estimation logic. However, the discrepancy between stated input requirements and the schema reduces completeness, and it does not describe the output schema despite its existence.

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 description adds context by explaining the inputs are used to derive complementary times, but it inaccurately states 'Inputs: target wake or bedtime' while the schema requires both fields, causing confusion. Schema coverage is 100%, but the description misrepresents usage.

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 estimates optimal bedtime or wake time based on 90-min sleep cycles, which is a specific verb and resource. It distinguishes from many sibling calculators but does not explicitly differentiate from other sleep-related tools like calculate_biorhythm.

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 advises 'Use for sleep optimization' and mentions inputs, which implies usage context. However, it does not specify when to prefer this tool over alternatives or provide exclusion criteria.

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