icu_get_wellness_data

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive nature. The description adds context that it returns a multi-day list, which is valuable beyond the annotations, though no further behavioral details (e.g., rate limits) are provided.

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 with 4 sentences, front-loaded with the core purpose, and every sentence adds value—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 tool's simplicity (1 optional parameter, 0 required, rich annotations, output schema present), the description fully covers its purpose, usage context, and return format without needing to detail output schema contents.

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 100% for the single parameter 'days_back' with default 7. The description only echoes the default and range behavior already in the schema, adding no semantic enrichment beyond what the input schema already conveys.

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 uses a specific verb ('Fetch') and resource ('wellness records over a RANGE of recent days'), clearly distinguishing it from siblings like icu_get_fitness_chart (CTL/ATL/TSB series) and icu_get_wellness_for_date (single date).

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?

Provides explicit when-to-use scenarios (trends, weekly summaries, recovery curves) and directs users to alternative tools for different needs (fitness chart via icu_get_fitness_chart, single date via icu_get_wellness_for_date), with example queries like 'how has my sleep been this week?'.

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