Fitbit Wellness Context

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it 'normalizes' data into a shared shape for recommendations, which provides some behavioral context beyond annotations, but does not elaborate on side effects or auth requirements.

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, front-loaded sentence of 18 words that efficiently conveys the core purpose. Every word is necessary.

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?

Although an output schema exists, the description does not clarify the 'wellness_context shape' or how parameters like 'soreness' and 'injury_flags' impact output. Given the tool's complexity (6 parameters, normalization logic), the description is too brief 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?

Schema description coverage is only 33% (2 of 6 parameters have descriptions), and the tool description does not explain any parameters. Agents must interpret 'soreness','injury_flags','notes' from names alone, lacking clear semantics.

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 verb 'Normalize' and the resource 'Fitbit sleep and activity load' into a 'shared wellness_context shape' for recommendation engines. This distinguishes it from sibling tools like fitbit_get_sleep_day and fitbit_daily_summary that provide raw or summary data without transformation.

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 implies usage when normalized data is needed for recommendation engines, but does not explicitly state when not to use or compare to alternatives like fitbit_daily_summary. The context is clear, but exclusions are missing.

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