garmin_badges

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

No annotations are provided, so the description carries the behavioral burden. It signals a read-only retrieval by describing returned content, and the presence of an output schema covers return-value structure. It doesn't confirm the operation is a safe read or mention pagination or scope limits, leaving mild gaps.

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?

Three short lines are front-loaded with the core content and earn their place by enumerating examples of what counts as a badge. There is minimal waste, though the final line 'Shows progression over time' is somewhat filler.

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?

For a parameterless read tool with an output schema defining the return shape, the description is nearly sufficient. It explains what badges represent and examples, missing only a note on read-only nature or scope, which the output schema largely covers.

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?

There are zero parameters, so the baseline is 4. Nothing needs explaining, and the description correctly doesn't invent parameter details.

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 names the resource ('Earned badges and achievements with dates') and adds categories like distance PRs and streaks. It's clearly about a read of badge/achievement data, but it doesn't distinguish from the closest sibling, garmin_records, which likely also surfaces PRs. The verb is implied (retrieve/list), not stated.

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 when-to-use guidance and no mention of alternatives. With garmin_records and garmin_challenges present as potential overlaps, the agent gets no help deciding which tool to call for milestone data.

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