create_run_hills_workout

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

No annotations are provided, so the description carries the full burden. It usefully discloses the key side effect ('upload it to Garmin Connect') and the effort-based (non-target) nature of the workout, but says nothing about authentication needs, whether an existing same-named workout is overwritten, error behavior, or whether uploading also schedules it.

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-loads the action and side effect, then uses a compact structured Args block. Every line earns its place; only minor trimming is possible.

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 creation tool with an output schema (so return values need no explanation), the description covers purpose, workout structure, and all parameters. Gaps around upload side effects (overwrite/schedule behavior) and permissions keep it from being fully 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?

Schema description coverage is 0%, so the description must compensate — and it does, documenting all six parameters with meaning, unit (seconds vs minutes), and defaults. It falls short of full marks only because it omits valid ranges/constraints for values like reps or hill_sec.

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 ('Create a hill repeat running workout') and additionally specifies the structure ('Hill reps with jog-down recovery') and the target mode ('No target — effort-based'). This clearly distinguishes it from siblings like create_run_intervals_workout or create_run_tempo_workout, which are paced/target-based.

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 'No target — effort-based' phrasing implies when this workout is appropriate versus target-based siblings, but no explicit when-to-use, prerequisites, or named alternatives are given. Usage is inferable rather than stated.

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