get_hrv_data

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds useful scope details like 'nightly' and 'COROS Training Hub dashboard', but it does not disclose other behavioral traits such as authentication requirements or how 'recent' is defined.

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, front-loaded sentence names the action, data scope, and source with no filler. Every word contributes to the agent's understanding.

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 zero-parameter, read-only tool, the description is largely complete: it states what data is returned and where it comes from. It could add the exact lookback window or return format, but those are not essential given the simple call signature and strong annotations.

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 tool takes no parameters, so there is no parameter burden for the description to carry. The schema coverage is trivially 100%, and the description's mention of HRV, baseline, and variability provides sufficient context for a zero-input read.

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 uses the specific verb 'Read' and names the resource ('recent nightly HRV, baseline and variability') plus the source ('COROS Training Hub dashboard'). This clearly distinguishes it from adjacent sibling tools like get_sleep_data or get_daily_metrics.

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 implies the tool is for retrieving recent HRV-related metrics, but it gives no explicit when-to-use guidance, exclusions, or alternatives. For a zero-parameter read this is workable, but the agent must infer when this tool is preferable to siblings.

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