Breathing rate

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read operation. The description adds that the tool returns waking, sleeping, highest, and lowest values, but it does not explain how an omitted or null date behaves or any data-availability caveats. No contradiction with annotations.

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 front-loaded sentence with no filler. It states the resource and scope first, then compactly lists the returned metrics, so every word 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?

For a simple read-only tool with an output schema and one optional parameter, the description adequately explains that it returns daily respiration metrics. The main gap is the underspecified date parameter semantics, which matters because the schema itself provides no description for 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?

Schema description coverage is 0%, so the description must compensate for the undocumented date parameter. Saying 'for a day' implies date selects the day, but it does not specify accepted date formats, the meaning of null, or what happens when the parameter is omitted. This is insufficient for the tool's only parameter.

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 identifies the resource (breathing rate) and the temporal scope (a day), and enumerates the specific measures returned (waking, sleeping, highest, lowest breaths per minute). It lacks an explicit verb like 'retrieves' and does not differentiate from siblings, but the intent is unambiguous.

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 daily scope and the enumerated metrics imply this tool is for per-day respiration summaries, and there is no dedicated respiration sibling among the listed tools. However, there is no explicit guidance on when to use it versus alternatives such as garmin_daily_summary or garmin_heart_rate, so usage is only implied.

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