create_run_tempo_workout

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that it uploads a new artifact to Garmin Connect and lists the defaults applied when args are omitted, but it says nothing about authentication/permission needs, idempotency, or what happens on a duplicate 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?

Purpose is front-loaded in the first sentence, followed by a compact, well-labeled Args block. Every line carries information; the only mild redundancy is restating the Z4 default already implied by the annotation-free schema.

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, and the description covers purpose, all parameters, and defaults for a creation/upload tool. The main gap is the absence of any behavioral caveats (permissions, upload failures) in the absence of annotations.

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?

With 0% schema description coverage the description must compensate, and it documents all five parameters individually, including an example value for name and the Z1-Z5 range for hr_zone (an enum the schema lacks). It adds real meaning beyond the bare parameter titles, though it doesn't clarify units or interaction between duration_min and the tempo block.

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?

Specific verb ('Create') plus precise resource ('tempo/threshold run workout') and an explicit side effect ('upload it to Garmin Connect'). It even differentiates from the sibling create_run_easy_workout by noting the higher HR zone default, so an agent can separate it from the other run-workout creators.

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 phrase 'tempo/threshold run' implies when this is appropriate, and the comparison to 'easy run' hints at the alternative, but it never states when to choose this over create_run_easy_workout, create_run_intervals_workout, or the other run-workout siblings. Usage is left to inference.

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