Daily summaries

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful operational context by naming the returned metric set and the 92-day per-call limit.

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 a single front-loaded sentence that names the resource, enumerates the metrics, and adds the key range limit. There is no wasted language.

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?

The description covers purpose, metrics returned, and the maximum range, while annotations handle the safety profile and the schema fully documents both parameters. It is complete enough to call correctly, though additional notes about missing-data behavior or timezone handling would make it fully comprehensive.

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 already documents both parameters at 100% coverage, including date format and the end_date default. The description adds meaningful semantic value by clarifying that the date parameters define a range and that the range may span up to 92 days per call.

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 states a specific resource and scope: daily totals over a range of days, with an explicit list of metrics. It is clear what the tool returns, but it does not explicitly distinguish itself from close siblings such as get_daily_overview or get_steps.

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 implies usage for multi-day daily aggregates and gives a maximum range of 92 days per call. However, it does not state when to use this tool versus alternatives like get_daily_overview, get_steps, or get_stress for similar data.

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