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

readOnlyHint=true already establishes the safe-read profile, and the description adds value beyond it: the shape of the returned data (resting HR plus time-in-zone) and the REST endpoint it wraps. It does not mention auth/scopes or rate limits, keeping it below 5, but it is a solid supplement to the annotation.

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 compact sentences, front-loading what the tool returns before the parameter rule. The raw REST path is arguably redundant for an agent and slightly pads the entry, but nothing else is wasted.

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?

With no output schema, the description carries the return-value burden and does so briefly (resting HR and per-zone time). All three parameters are fully documented in the schema and the read-only annotation covers safety, so an agent has what it needs to call it correctly.

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 100%, so the schema already documents date, period, and endDate including the period-vs-endDate precedence. The description restates the same date+period/date+endDate rule without adding format or edge-case detail, so the baseline 3 applies.

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 resource ('Heart-rate time series') and names the concrete payload ('resting HR and time in each HR zone'), which lets an agent distinguish it from fitbit_hrv and fitbit_cardio_score. It stops short of explicitly naming those siblings as alternatives, so it is clear but not sibling-differentiated at the 5 level.

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 gives invocation guidance ('Give a single date + period, OR a date + endDate range'), which tells the agent how to combine parameters. It does not say when to prefer this tool over fitbit_hrv, fitbit_cardio_score, or fitbit_daily_activity_summary, and gives no exclusions, so usage is implied rather than explicit.

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