Garmin Daily Steps Chart

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds that it returns a summary chart, which is useful but does not disclose additional behavioral traits like data granularity or caching. With annotations covering safety, a 3 is appropriate.

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?

A single, front-loaded sentence with no redundant information. Every word is necessary: 'Get Garmin daily steps and summary chart for a date.' Perfectly concise.

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?

With an output schema present, the description need not detail return values. However, it does not clarify what a 'summary chart' entails (e.g., markdown table or image). The tool has 3 parameters and no required ones; the description is minimal but adequate for basic 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 coverage is 67% (missing description for response_format). The description does not explain any parameters. However, the schema provides enums and defaults for all parameters, making them fairly clear. The description adds no extra meaning, so a baseline 3 is given.

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 retrieves daily steps and a summary chart for a given date. The verb 'Get' and resource 'Garmin daily steps and summary chart' are specific. Among siblings like heart or sleep, the name and description distinguish it, but without explicit differentiation it loses a point.

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?

No guidance is provided on when to use this tool versus alternatives like garmin_get_heart_day or garmin_get_sleep_day. The description implies it's for steps, but lacks explicit context or exclusion hints.

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