health_get_breathing_rate

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

Discloses caching behavior (returns from cache, auto-syncs if stale) and output format (one entry per night), which are important behavioral details not available in annotations (none provided).

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 concise and well-structured, though it repeats parameter details that could be considered redundant. Overall, it is clear and not overly verbose.

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?

Provides comprehensive context: purpose, parameter details, output structure, caching, and even a clinical note. Given no annotations or schema descriptions, it fully equips the model to use the tool correctly.

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?

Each parameter (start_date, end_date, live) is fully explained with format, default, and semantic meaning, compensating for the lack of schema descriptions.

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?

Clearly states it retrieves nightly breathing rate (avg breaths per minute during sleep), with a specific verb and resource. Distinguishes from sibling tools by the metric.

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 a use case (illness/recovery signal) but does not explicitly mention when to use this tool instead of alternatives or when not to use it. The guidance is implicit rather than explicit.

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