Get SpO2

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context by warning that include_samples returns every individual reading and is large, which helps an agent avoid unnecessarily heavy calls.

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 compact and front-loaded: the returned metrics come first, followed by concise parameter notes. Every sentence adds useful information with no redundancy.

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 two-parameter read-only wellness query, the description is nearly complete: it enumerates the return metrics, explains both parameters, and warns about large sample payloads. It does not describe response structure, but no output schema exists and the metric list provides adequate orientation.

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, and it does: date is documented as YYYY-MM-DD with a default of today, and include_samples is explained as returning every individual reading, with a size warning. Both parameters are covered semantically.

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?

States a specific resource and verb-like action: retrieves blood oxygen (pulse ox) for a day, listing the exact metrics returned. It is clearly distinguishable from siblings such as heart rate, HRV, and stress, though it does not explicitly name alternatives.

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?

Provides clear context with the date default and the include_samples option, but gives no explicit when-to-use/when-not-to-use guidance versus sibling wellness tools. Usage is implied rather than prescribed.

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