calculate_sleep_cycles

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

With no annotations, the description carries full burden. It states returns 4-6 cycle recommendations, but does not disclose any side effects, authentication needs, or limitations beyond that. Behavioral disclosure is minimal.

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 short and front-loaded with the purpose. The reference to 'list_bundles' adds some noise but is not excessive. Could be more concise by removing or integrating the last sentence.

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?

There is an output schema, so return values are partly covered. However, the description contradicts the schema on required parameters, making it incomplete. No guidance on edge cases or behavior when both inputs are provided.

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 says 'Inputs: target wake or bedtime' implying either/or, but the schema requires both bedtime and wake_time. This contradiction misleads the agent about parameter usage. The schema descriptions are present (bedtime HH:MM, wake time HH:MM) but the description undermines them.

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-minute sleep cycles, with a specific verb and resource. It distinguishes itself from the many sibling 'calculate_' tools by being sleep-specific.

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 says 'Use for sleep optimization' and 'Inputs: target wake or bedtime', providing clear context. It does not explicitly exclude alternatives, but it references 'list_bundles' for related calculators, offering some guidance.

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