get_respiration

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It describes the output metrics well (average, min, max, waking vs. sleeping) but does not mention that the tool is read-only, data freshness, or any permissions needed. This is adequate but not thorough.

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 extremely concise, with a single sentence summarizing the output followed by a clear parameter definition. No wasted words; every sentence adds value.

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?

Given the tool has an output schema (not shown), the description does not need to detail return values. It already provides a good overview of the metrics returned. The context is simple (one optional parameter), and the description is complete enough for an AI agent to understand what the tool does and how to use it.

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?

There is one optional parameter 'date' with 0% schema description coverage. The description compensates fully by specifying the format ('YYYY-MM-DD') and default behavior ('Defaults to today'), adding significant meaning beyond the raw schema type.

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 clearly states the tool returns daily respiration rate with specific metrics (average, min, max, waking vs. sleeping averages). The verb 'get' and resource 'respiration' are explicit. It distinguishes from sibling tools like get_sleep and get_hrv_status which cover different health 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?

No guidance on when to use this tool versus alternatives. The description only explains what it does, not context or prerequisites. For a health metrics tool, mentioning that it provides respiratory data as opposed to heart rate or sleep would help, but is absent.

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