get_daily_metrics

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns 'complete unprocessed response' and 'ALL raw health metrics,' which is key behavioral context. However, it doesn't mention potential large response size, rate limits, or error behavior, leaving some gaps.

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 two concise sentences. The first states the purpose and scope, the second gives usage guidance. No redundant words, front-loaded with the core action, and every sentence 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 retrieval tool with three optional parameters and no output schema, the description is reasonably complete but leaves ambiguity about what 'raw health metrics' actually includes. It also doesn't explain how the date parameters interact (single date vs range), though the schema covers their formats.

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?

The input schema already provides full coverage (100%) with clear descriptions for date, end_date, and start_date. The description adds no extra parameter semantics beyond hinting at raw data retrieval, so baseline 3 is appropriate since the schema does the heavy lifting.

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 resource 'ALL raw health metrics from the Ultrahuman API,' making the purpose specific. It also distinguishes from sibling tools by emphasizing the 'complete unprocessed response' and directing use to cases where other tools don't expose the needed 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?

The description explicitly says 'Use this only when you need access to data not exposed by other tools,' which gives clear when-to-use guidance and implies alternatives (other specific tools). It lacks explicit when-not-to-use examples but the 'only when' phrasing covers the main exclusion.

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