garmin_wellness_activity

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

No annotations, so the description carries the full burden. It discloses the payload contents (start/end times, activity type) which is useful behavioral context, but says nothing about auth needs, rate limits, or default time window behavior. Partial disclosure against full burden.

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 short sentences, front-loaded with the core resource definition, and no filler. The second sentence is slightly redundant on the separation point but still earns its place.

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?

An output schema exists so return value structure need not be explained, and the tool is simple (1 param). However the undocumented 'days' parameter and the absence of any usage routing leave gaps for an agent with many overlapping activity siblings.

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?

The single parameter 'days' has 0% schema description coverage and no default is explained as a lookback window. The description never mentions time-range scoping at all, so it fails to compensate for the undocumented parameter.

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?

States a specific resource (wellness activity sessions) with concrete examples (yoga, breathwork) and explicitly distinguishes these non-sport sessions from regular activities. This gives good differentiation from siblings like garmin_activities, though it does not name them directly.

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 clause 'tracked separately from regular activities' implies when this tool applies versus the general activity tools, but no explicit when-to-use condition or named alternative is given. Usage is inferable rather than instructed.

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