get_daily_summary

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

No annotations are provided, so the description carries the full burden. It describes the tool as a summary aggregation, which is a read-only operation. However, it does not disclose potential edge cases (e.g., missing data for a day) or any authentication requirements. For a simple read tool, this is adequate but not exceptionally transparent.

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 extremely concise: three sentences plus a parameter list. It is front-loaded with the most important information (purpose and metrics), and every sentence is necessary. No wasted words.

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?

Given the tool's low complexity (1 parameter with default, no required params, no nested objects) and the presence of an output schema, the description is complete. It covers what the tool does, when to use it, and how to invoke it. The agent can confidently select and use this tool.

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 schema has 0% description coverage, but the tool description includes an 'Args' section that explains the 'day' parameter with examples ('today', 'yesterday', '3 days ago', '2026-08-18'). This adds significant meaning beyond the schema's type and default, 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?

The description clearly states the tool returns an 'overall summary of one day' and lists the specific metrics included (steps, calories, heart rate, etc.). This specific verb+resource combination distinguishes it from sibling tools like get_steps, get_sleep, which return individual metrics.

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: 'Start here when the user asks "how was my day" or "how am I doing today".' This tells the agent exactly when to use this tool. While it doesn't explicitly state when not to use, the sibling list implies alternatives for specific metrics or date ranges.

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