getHrvRange

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

No annotations exist, so the description carries the full disclosure burden. It implies a read-only retrieval and states the data is daily/overnight, but says nothing about return shape, missing-data behavior, date-range limits, or whether ranges are inclusive.

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?

A single compact sentence with the resource and the date format front-loaded and no filler. It is telegraphic enough that it reads more like a fragment than a complete instruction.

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 simple two-parameter read tool with full schema coverage, the essentials are present, but with no output schema the agent gets no hint about the returned HRV fields or aggregation. Adequate but with a clear gap.

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%, with both fromDate and toDate documented as yyyy-MM-dd, so the description's format note is redundant rather than additive. Baseline 3 applies since the schema already does the work.

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?

Names a specific resource (daily overnight HRV summaries) and scope (date range), which clearly separates it from siblings like getSleep or getDailyHeartRate. It never explicitly contrasts itself with those siblings, keeping it short of a 5.

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?

There is no guidance on when to use this versus getDailySummary, getSleep, or other date-range health tools, and no stated prerequisites. The date-range scope is implied by the parameter names rather than explained.

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