garmin_sync

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

With no annotations, the description carries full burden and does well: it discloses the background execution (~2 minutes), that the first call returns status 'started', and the required follow-up call, explaining the timeout rationale. It omits edge cases like concurrent-sync behavior or failure states, keeping it short of 5.

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?

Front-loaded with the core action, then behavior, then use cases. Every sentence adds value, though the parenthetical about Claude Desktop timeouts is slightly verbose for the space it occupies.

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?

An output schema exists so return values need no explanation; the description covers purpose, timing, the parameter, and invocation triggers. It is complete enough for correct use, with only minor gaps around error/concurrency handling.

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 single parameter has 0% schema description coverage, so the description must compensate, and it does: 'Set refresh=False to just check the current state and last sync result without triggering a new sync' fully explains the flag's semantics.

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 specific verb and resource ('Sync the latest data from Garmin Connect'), and the async-refresh behavior makes it clearly distinct from the read-only siblings (garmin_query, garmin_activities, etc.) that only fetch already-synced data.

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?

Provides an explicit 'Use this when:' list with three concrete triggers (just finished a run/ride, want today's health data loaded, data looks outdated) and clarifies the refresh=False mode. It stops short of naming alternatives or stating when NOT to use it, but the context is clear.

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