garmin_sync

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

The description adds a behavioral warning about rate-limiting on Garmin's unofficial API, which is not covered by the annotations. It also specifies the scope of data synchronized. The annotations already indicate the tool is read-only, idempotent, and non-destructive, so the description complements these without contradiction.

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 two short sentences with no redundant information. It front-loads the purpose and then adds a necessary caution, making it well-structured and concise.

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?

Given the tool's simplicity (one optional parameter), the presence of rich annotations, and an output schema, the description covers the core functionality and a key operational concern. It doesn't explicitly state that this tool should be called before using getter tools, but that is implied by its role among siblings. Overall, it is sufficiently complete.

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 description does not mention the 'days' parameter, and the schema has no description for it (0% coverage). The tool's single parameter name is somewhat self-explanatory, but the description fails to explain how it controls the synchronization range (e.g., 'recent' could mean different values). This is a clear gap that the description should have filled.

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 a specific action: synchronize recent Garmin daily summaries and activities into the local cache. It includes a verb, resource, and destination, distinguishing it from sibling tools that focus on reading/querying 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?

The description advises to 'use sparingly' due to potential rate limiting, which is a clear usage instruction. However, it does not explicitly name alternative tools or mention when not to use this tool, though the group of sibling tools suggests it is for populating the cache for later reads.

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