get_daily_metrics

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the daily metric scope and date range, but it does not disclose return shape, timezone handling, pagination, or aggregation behavior. This is adequate but not rich.

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 a single, properly front-loaded sentence with no filler. It states the action, the resource, and the key scope efficiently.

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?

This is a relatively simple two-parameter read tool, and annotations cover the read-only/destructive aspects. However, the description still omits date format details and return value expectations, and it does not help disambiguate from similar health-metric siblings.

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 0%, so the description must compensate for startDate and endDate. It only says 'for a date range,' which does not add meaningful information beyond the parameter names. Date format, inclusivity, timezone, and range limits are all missing.

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 a specific verb ('Read') and names a concrete resource: COROS daily HRV, resting heart rate, fatigue, training load, load ratio, and fitness metrics for a date range. It is clear what the tool does, though it does not explicitly distinguish itself from overlapping siblings like get_hrv_data or weekly_training_report.

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 only implies usage with 'for a date range' and provides no explicit when-to-use or when-not-to-use guidance. It does not name alternatives or explain why an agent should choose this over other metric-focused sibling tools.

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