create_strength_workout

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

No annotations provided, so description carries full burden. It discloses that the tool is a write operation, requires confirmation token, and that the workout lands in library but not immediately on watch. Could mention idempotency or side effects, but sufficient context is given.

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?

Well-structured with clear bullet points and separate sections. Every sentence adds value, no fluff.

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 complexity (nested schema, 3 params, write operation), the description covers the workflow, prerequisites, parameter meanings, and caveats. Output schema exists, so lack of return value explanation is acceptable.

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?

Description clarifies that 'workout' shape is same as preview, 'confirmation_token' binds to exact preview, and 'confirm' is for dev/stdio only. The input schema descriptions are detailed, but the description adds crucial behavioral context beyond schema.

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?

Description clearly states it creates a strength workout in Garmin Connect library, explicitly calling it a WRITE. This distinguishes it from the sibling tool 'preview_strength_workout', which is for previewing.

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?

Explicitly states prerequisites: writes must be enabled and a matching confirmation_token from preview_strength_workout is required. Also explains the workflow: preview then create, and that the workout reaches the watch only after manual send/sync.

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