Summarize health record

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

Annotations already indicate readOnlyHint and idempotentHint. Description adds that it returns computed descriptive data only and never a diagnosis, which provides valuable behavioral context beyond annotations. No contradictions.

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 sentences. First sentence front-loads purpose and output components; second adds context and constraints. Every phrase earns its place with 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 presence of an output schema, description covers the important aspects: what's included (profile, stats, trend, events, notes) and what's excluded (diagnosis). With zero required parameters and optional window, this is complete for an agent to understand the tool's role.

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?

Input schema has 3 parameters (user, since, until) but description only hints at 'over a window' for time parameters and does not explain user default behavior or date format. With low schema coverage (33%), description should compensate but does not add sufficient meaning.

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?

Description clearly states the verb (produce), resource (digest of user's whole record), and specifics (profile, per-metric statistics+trend, recent events grouped by category, recent notes). It distinguishes itself as the primary tool for LLM reasoning over health data.

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 it's the primary tool for LLM reasoning, implying when to use. Also clarifies it returns computed data only (no diagnosis). Does not explicitly mention when not to use or alternatives, but context provides adequate guidance.

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