get_respiration_data

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, and the description mostly repeats read-only while adding Garmin Connect as the source. It does not clarify what 'available' means, missing-data behavior, timezone handling, or any auth/rate-limit context.

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 definition is short, but the date format is stated twice and the first sentence is awkwardly phrased. The parenthetical repeats read-only and date-format information already present, so not every sentence fully 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 single-date read operation with annotations covering safety and an output schema covering return values, the description gives enough to invoke it: Garmin Connect source, read-only nature, and cdate format. Remaining gaps are minor ambiguities around data granularity and availability semantics.

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 carry parameter meaning; it gives the required format YYYY-MM-DD for cdate but does not explain that cdate represents a single calendar date or any constraints around availability. It partially compensates but leaves the parameter name and scope unclear.

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 states a specific verb and resource: return available respiration data from Garmin Connect. It is clear enough to distinguish from siblings by resource name, though it does not explicitly contrast with nearby tools like get_spo2_data or get_stress_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?

There is no explicit guidance on when to use this tool versus alternatives, nor any stated exclusions or prerequisites. Usage is only implied by the tool name and the required date parameter.

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