List recoveries

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

Annotations already cover safety (read-only, idempotent, non-destructive). The description adds ordering and metric scope, but says nothing about pagination behavior (next_token) or raw-vs-summary output, though those are documented in the schema descriptions.

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 that carries the metric list and ordering with zero waste. Every clause earns its place.

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?

Complete enough for a read-only list tool: what it returns, in what order, and the metrics. Missing only explicit tie to the raw/summary and pagination behaviors, which the schema covers. No output schema, but the description enumerates the fields, so return shape is sufficiently implied.

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 parameter meaning is already fully documented in the schema (start/end/days/limit/next_token/raw). The description adds no parameter details beyond the schema baseline.

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 recovery scores), enumerates the exact metrics returned (HRV/RMSSD, RHR, SpO2, skin temp), and states sort order. Clearly distinguished from siblings like list_cycles, list_sleeps, list_workouts, which return different resources.

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?

Usage is implied by the resource list and 'most recent first' ordering, but there is no explicit when-to-use vs alternatives such as get_daily_overview or get_trends, and no note on when to prefer one over the other.

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