List Raw Health Data Points

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

Description adds behavioral context beyond annotations: confirms read-only nature, explains pagination defaults (most recent first, max pages/ page size limits), and notes raw filter complexity. No contradictions with annotations.

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 concise paragraphs with no redundant sentences. Every sentence adds distinct information: purpose, use cases, parameter behavior, and alternative. Well-structured for quick reading.

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?

Covers all necessary aspects given tool complexity: purpose, parameters, usage guidelines, and behavioral quirks. No output schema exists, so return value details are omitted, but context is sufficient for correct invocation.

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 descriptions already cover all 4 parameters with 100% coverage. Description adds value by mapping common keys to raw dataType strings and clarifying the filter parameter's obscurity, enhancing usability.

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 fetches raw health data points with finer-than-daily granularity, distinguishing from get_daily_summary by mentioning intraday data and dataType coverage. The verb 'fetch' and specific resource (raw data points for a single Google Health dataType) are precise.

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?

Explicitly states when to use (finer granularity, unsupported dataTypes) and when to use alternative (get_daily_summary for trends). Provides clear guidance with comparative cost hint ('far cheaper'), aiding selection.

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