get_gear

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the data returned (shoes/bikes, total distance, activity counts) but does not explicitly state that this is a read-only retrieval, how gear is scoped, or whether any authentication or sync behavior is involved. The description adds limited context beyond the tool name.

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 one concise sentence that front-loads the core resource ('Gear registered in Garmin Connect') and then clarifies the target items and included metrics. Every word earns its place, with no wasted content.

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 zero-parameter tool with an output schema, the description covers the resource and key return metrics, so invocation is possible. However, it lacks usage context and fails to distinguish itself from related sibling tools, leaving the agent without guidance on when this is the right choice.

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 baseline is 4. The description adds useful context about the returned fields (total distance and activity counts), which is more than the empty schema alone provides.

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 states that the tool returns gear registered in Garmin Connect, specifically shoes and bikes, with total distance and activity counts. This clearly identifies the resource and scope. It does not explicitly contrast with the sibling tool get_activity_gear, so it stops short of full sibling differentiation.

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 guidance on when to use this tool versus alternatives such as get_activity_gear or other gear-related endpoints. No context about prerequisites, account requirements, or exclusions is provided. The agent must infer usage solely from the tool name.

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