Garmin Respiration

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds 'when available' indicating potential absence of data, and 'Not medical advice' is a disclaimer. This provides some extra context but does not significantly extend beyond 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 sentence with a necessary disclaimer, efficiently conveying the core purpose without unnecessary details. It is front-loaded with the action and resource.

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 3 optional parameters and an output schema, the description is minimal. It does not explain what respiration data includes (e.g., RR intervals, breathing rate) or the implications of privacy_mode. Compared to sibling tools, it could benefit from more details, but output schema may compensate.

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 67% (date and privacy_mode have descriptions; response_format does not). The tool description does not elaborate on param meanings or usage beyond schema, missing opportunity to clarify privacy_mode and response_format defaults or effects.

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 verb 'Get' and the resource 'Garmin respiration data', with a condition 'for a date when available'. This distinguishes it from sibling tools like garmin_get_heart_day and garmin_get_sleep_day, avoiding tautology.

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 provides no guidance on when to use this tool versus alternatives. It mentions 'when available' but does not specify prerequisites, limitations, or compare with similar tools like garmin_get_respiration_day v.s. garmin_get_stress_day.

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