Get Respiration Data

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

The annotations already declare readOnlyHint=true and openWorldHint=true, lowering the burden. The description adds useful behavioral context beyond that by specifying the output measure ('breaths per minute') and temporal coverage ('throughout the day and during sleep'), though it does not discuss missing-data behavior.

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 concise, front-loaded sentences with no filler. Each sentence adds value: the first states the primary action and resource, and the second clarifies the output unit and coverage.

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 low-complexity tool with one optional parameter and no output schema, so the description adequately covers what data is returned ('breaths per minute throughout the day and during sleep'). It does not specify response structure, but the phrasing is sufficient for the tool's simplicity.

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 schema fully documents the single parameter, including format and default-to-today behavior, so schema coverage is 100%. The description merely says 'for a specific date,' which mirrors the schema and adds no new parameter semantics.

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 explicitly names the resource ('respiration/breathing rate data'), the action ('get'), and the temporal scope ('for a specific date'), while also stating the unit ('breaths per minute'). This clearly distinguishes it from sibling health-metric tools like get_hrv_data or get_spo2_data.

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 clear context: use it to retrieve respiration/breathing data for a specific date, covering both daytime and sleep periods. It does not explicitly name alternatives or exclusion cases, but the focus on 'respiration/breathing rate data' makes the intended use case evident.

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