garmin_gear

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

The description discloses that the tool returns cumulative mileage per gear item. With no annotations, this is credible but lacks explicit mention of read-only behavior, authorization needs, or side effects. It adequately describes the primary output but omits potential constraints.

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, efficient sentence that conveys the tool's core function. It is front-loaded with the verb 'Get' and the resource. However, it could be slightly expanded to clarify 'real cumulative mileage' without being verbose.

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?

The tool is simple with no parameters and no output schema. The description covers the basic purpose but does not mention response structure, possible empty results, or pagination. It is minimally complete but leaves room for ambiguity about the output format.

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 tool has zero parameters, so the description does not need to explain parameter semantics. According to guidelines, baseline for 0 parameters is 4. The description adds no parameter-related information, which is acceptable.

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 a gear library (shoes, bikes, etc.) with cumulative mileage. It identifies the resource (gear library) and specific output (mileage). While it distinguishes from siblings like garmin_activities, it could be more explicit about what 'gear library' encompasses.

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 such as garmin_activities or garmin_health. The description implies use when gear data is needed, but no exclusions or comparisons are given.

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