garmin_request_reload

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

Beyond the annotations, "Ask Garmin" and "reprocess" convey that this triggers a Garmin-side operation rather than merely reading local data. It does not clarify whether processing is asynchronous, how soon corrected numbers may appear, whether repeated requests are safe, or what data types are affected.

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 single sentence is compact and front-loads the operation before the usage condition. Every phrase contributes either to understanding the action or deciding when to invoke it.

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 simple one-parameter tool, the description and fully documented schema provide enough information to select and invoke it correctly. The main remaining gaps are operational: the scope of reprocessed data, expected completion behavior, and how to verify the reload, with no output schema supplying those details.

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%, and the date parameter already documents its accepted formats. The description reinforces that the date identifies the day to reprocess but adds no parameter details beyond the schema, so the high-coverage baseline applies.

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 action and resource: asking Garmin to reprocess one day's data. Its reprocessing purpose is distinct from the many retrieval and logging siblings, though it does not explicitly contrast itself with any particular alternative.

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 parenthetical "when a day's numbers look stuck or wrong" gives a concrete condition for using the tool. It does not explain when not to request a reload, such as for ordinary data retrieval, or name an alternative for checking the resulting data.

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