get_badge_detail

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds substantial context beyond them: positive-integer validation on badgeId, and the non-obvious error contract that an unknown id returns a 400 GarminHttpError rather than a 404. It also enumerates what each relatedBadges entry carries, which is real behavioral disclosure.

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 verb, endpoint and resource are front-loaded, and the sentence is dense but organized. It is long, but since there is no output schema the return-field detail is largely earning its place rather than padding.

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 no output schema, the description carries the return-shape burden and does so (getEarnedBadges fields plus relatedBadges, assoc fields, followings, badgeImageUrls), and it documents validation and error behavior. Only the origin of a valid badgeId is left implicit.

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 0% (the single badgeId property is an undocumented number), so the description must compensate. It adds the meaningful constraint that badgeId is validated as a positive integer, which is not in the schema, though it does not indicate where a valid badgeId is sourced from.

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 concrete verb (GETs) and resource (the badge detail v3 endpoint), and clarifies scope with 'Works for unearned badges', which an agent needs to distinguish it from get_earned_badges/get_available_badges. The purpose is unambiguous without opening the schema.

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?

Usage is implied rather than stated: the note that it 'works for unearned badges' and the reference to getEarnedBadges for field semantics hint at context, but there is no explicit when-to-use/when-not or naming of the retrieval siblings. Adequate but with a clear gap.

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