get_cycles

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

With no annotations, the description carries full behavioral burden. It usefully discloses domain semantics (the 0–21 strain scale) and that the latest cycle may still be in progress, but it does not state read-only behavior, permissions, or return shape beyond the two fields.

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 sentences, front-loaded with the core return value before the usage note and domain scale. Every sentence adds useful information without repetition.

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?

For a single-parameter read tool with no output schema and no annotations, the description covers the essential purpose, domain interpretation, and an in-progress caveat. Only minor gaps remain, such as not distinguishing it from sibling physiological tools.

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 days parameter is already fully documented with min/max/default. The description's 'last N days' adds no new syntax or format detail beyond 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?

States a specific verb and resource: returns daily physiological cycles with day strain and average heart rate for the last N days. This clearly identifies the tool's function, but it does not explicitly distinguish it from siblings like get_recovery or get_sleep, which also return physiological data.

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 sentence 'Use it to see overall daily strain' gives an implied use case, but there is no explicit guidance on when to choose this over get_recovery/get_workouts 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.