Heart rate (hourly)

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

Annotations already indicate readOnlyHint=true, so description doesn't need to restate. It adds valuable behavioral details: aggregation per hour, included metrics (avg/min/max bpm, sample count), and range limits (3-day cap). No contradictions.

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 sentences with no wasted words. The first sentence states the purpose and output, the second gives usage guidance and alternatives. Well-structured and front-loaded.

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 read-only tool with two simple parameters and no output schema, the description adequately covers what is returned, the time range behavior, and when to use alternative tools. No gaps identified.

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 baseline is 3. Description adds value by stating the 3-day range cap (not in schema) and reinforcing defaults. However, it does not add new semantics beyond what schema already provides for the parameters themselves.

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?

Description clearly states the tool returns heart rate aggregated per hour with avg/min/max bpm and sample count. It specifies the scope (across day and night) and distinguishes from sibling oura_get_sleep_detail for sleep-time heart rate.

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?

Explicitly says use for 'what was my pulse today/this afternoon' and advises to prefer oura_get_sleep_detail for sleep-time heart rate. Also notes the range is capped at 3 days and defaults to the last 24 hours.

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