garmin_connect_api

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

There are no annotations, so the description carries the full behavioral burden. It transparently reveals that this is a raw arbitrary-path passthrough and documents GET/POST plus optional body. However, it omits important behavioral context such as authentication requirements, error behavior, and the potential side effects of a POST to an arbitrary endpoint.

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 compact and front-loaded: first sentence states the core purpose, second sentence gives the usage rule, and the parameter lines add just enough detail. No wasted words.

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 output schema covers return-value structure, and the description covers path, method, and body. However, for an arbitrary raw API tool, it should at least mention prerequisites like an active Garmin session/login and the absence of endpoint validation, both of which matter for correct invocation.

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 0%, so the description must compensate, and it does. It provides concrete path examples, states valid methods (GET or POST), and explains that body is an optional JSON string for POST. This adds meaningful semantics beyond the raw schema fields.

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's specific verb and resource: 'Call the Garmin Connect API at an arbitrary path.' It also differentiates itself from the specialized sibling tools by explicitly positioning itself as the fallback for 'endpoints not wrapped by other tools,' so an agent can distinguish when to use this tool.

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?

The description gives an explicit usage rule: use for endpoints not wrapped by other tools. This provides a clear when/when-not boundary. It doesn't name specific sibling alternatives, but the rule itself covers all the specialized siblings as a category.

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