garmin_gear

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds nothing behavioral beyond that: it does not say whether all gear is returned or a subset, whether stats are always included, or how a missing gear registry is handled. Without an output schema, a bit more disclosure about what comes back would have been valuable.

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?

It is short and front-loads the noun list, with no filler sentences. However, the telegraphic colon-list style crosses from concise into under-specified; a single verb would have made it both shorter in effort and far clearer.

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 low-complexity (0 required params, no nesting, no output schema), so full documentation is not needed. Still, the description leaves open whether the result is a list of all gear items, whether it includes retired gear, and what the stats fields contain — gaps an agent would hit on first call.

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 description coverage is 100% for the single optional parameter (include_stats, default true, documented in-schema), so the baseline of 3 applies. The description's 'total distance' phrase loosely corresponds to that flag but does not clarify the default behavior or trade-off, so it adds no meaning beyond the schema.

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 is a noun-phrase fragment ('Shoes, bikes and other gear: status, default activity types, total distance') that names the resource and hints at the data returned, but supplies no verb, so an agent cannot tell whether it lists gear, fetches one item's detail, or aggregates stats. It also does not differentiate from the sibling garmin_devices, which plausibly covers overlapping hardware.

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?

There is no when-to-use guidance, no statement of preconditions, and no pointer to an alternative tool. An agent choosing between garmin_gear and garmin_devices or garmin_activities gets no routing signal from this text, which is especially costly given the large sibling set.

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