Google Health Daily Rollup

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds context about daily aggregation but does not disclose pagination, rate limits, or error behavior beyond what annotations provide. It is adequate but not enhanced.

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 sentences, efficient and to the point. It includes the core action and use cases. Slight lack of structure (e.g., no bullet points) but 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 complexity (9 parameters, output schema, many siblings), the description covers only the basic purpose and example data types. Missing details on how window_size_days interacts with dates, pagination, and return format beyond the schema. Adequate but not fully complete.

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?

Schema coverage is 33%, meaning 9 parameters exist but description only implicitly covers data_type via examples. Other parameters (start_date, end_date, page_size, etc.) lack explanation in the description. The schema has detailed descriptions for some, but the tool description should compensate for low coverage more actively.

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 it aggregates data types over civil days and lists examples (steps, distance, etc.). However, it does not differentiate from siblings like 'google_health_daily_summary' or 'google_health_rollup', which weakens the distinctiveness.

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 suggests when to use (for these data types) but does not provide explicit when-not or alternatives. Among siblings, there are similar tools without clear guidance on choice.

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