Get Daily Summary

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

Annotations already indicate read-only and open-world behavior, so the bar for disclosure is lower. The description adds useful context that this is a compact/summary view versus detailed series, and names the specific alternative for detailed heart rate data.

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 sentences, no filler. The first sentence states the tool's output, and the second sentence gives a clear pointer to the sibling tool for more granular data. Every part 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?

There is no output schema, so the description's enumeration of returned metrics is important and provided. The optional date parameter and lack of detail about default behavior are minor gaps, but the tool is otherwise adequately described for a read-only summary endpoint.

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?

There is only one parameter, date, and the schema already fully describes its format with 100% coverage. The description does not add extra semantics beyond implying the summary is daily, so the schema carries the burden and the baseline of 3 is appropriate.

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 identifies the tool as retrieving a 'compact daily summary' and enumerates the contained metrics (steps, calories, distance, heart rate, stress, body battery, time breakdown). It also explicitly distinguishes itself from get_heart_rate, which provides the full heart rate series.

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 provides explicit guidance to use get_heart_rate when the full heart rate series is needed, which helps differentiate from a sibling tool. It does not enumerate all other alternative tools, but the primary competing use case is addressed.

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