Garmin Wellness Context

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering safety and idempotency. The description adds no further behavioral context (e.g., side effects, auth requirements), but it does not contradict annotations. A score of 3 is appropriate given minimal additional value.

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 a single, concise sentence (15 words) that efficiently communicates the tool's purpose. Every word is essential, and there is no wasteful repetition.

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?

Despite the presence of an output schema (which may define the return format), the description leaves many gaps: the normalization process, what 'movement load' is, and how optional parameters like 'soreness' influence output. With 6 parameters and low schema coverage, more context is needed for full understanding.

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?

Only 2 of 6 parameters have schema descriptions (33% coverage). The description does not elaborate on any parameters, such as the purpose of 'soreness', 'injury_flags', 'notes', or 'response_format'. With low schema coverage, the description should compensate but fails to do so.

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 tool's action ('Normalize') and the specific Garmin data sources (readiness, sleep score, Body Battery, recent movement load) and the target format (shared wellness_context shape for recommendation engines). This distinguishes it from sibling tools that retrieve individual metrics.

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 does not provide any explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. It implies usage for recommendation engines but lacks clarity on context and exclusions.

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