get_spo2

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the personal-API scope, but says nothing about read-only semantics, pagination or volume limits for a 1-30 day window, or what happens when no SpO2 data exists.

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 short sentences with no filler, and the metric identity is front-loaded. It is telegraphic to the point of under-specification rather than padded, but nothing is wasted.

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?

An output schema exists, so return formatting need not be explained, and the one optional parameter is fully specified in the schema. Still, for a health-metric tool with no annotations, the description should clarify what "acclimation" values represent and whether data is daily-aggregated or sparse.

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 coverage is 100% and the single "days" parameter already documents its meaning, default of 7, and 1-30 bounds. The description adds no additional detail (e.g., aggregation method or timezone handling), so the baseline 3 applies.

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?

"Blood oxygen (SpO2) acclimation per day" names the resource and the granularity, which separates it from metric siblings like get_hrv_history and get_steps_history. However, there is no verb and "acclimation" is an unusual framing whose meaning is not clarified, so the agent knows the topic but not exactly what is returned.

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?

"Personal API only" is an access constraint, not usage guidance. Nothing states when to call this versus get_health_summary, get_full_snapshot, or get_recovery, and no preconditions or exclusions are given.

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