Google Health Daily Rollup

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's brief 'aggregate' is consistent but adds little new behavioral context. It does not disclose pagination details, rate limits, or response structure beyond what is obvious from the name.

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, using only two sentences with no unnecessary words. It front-loads the core action and examples.

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 has 9 optional parameters and an output schema, the description lacks guidance on how to use date ranges, pagination, or parameter combinations. It is not sufficient for an agent to invoke this tool correctly without additional context.

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?

With schema description coverage at only 33%, the description should compensate by explaining parameters, but it only lists a few example data types. It does not clarify defaults like start_date='today' or end_date meaning, nor the role of page_size or window_size_days.

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 'aggregate' and the resource 'data type over civil days', and lists specific use cases like steps, distance, calories. However, it does not differentiate from sibling tools such as 'google_health_daily_summary' or 'google_health_rollup', leaving potential ambiguity.

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 when to use by listing example data types, but it does not provide explicit guidance on when not to use this tool or alternatives. There is no mention of prerequisites or comparison with other tools.

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