create_running_workout

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

No annotations provided, so description carries full burden. It discloses the write nature, prerequisite token, and that the workout lands in the library. Also notes the dev-only confirm flag. While not exhaustive (e.g., reversibility, failure modes), it covers the critical behavioral traits for safe usage.

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?

Description is well-structured with an overview and an Args section. Sentences are purposeful; no fluff. Although moderately long, it earns its length given the tool's complexity.

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 complex nested input schema and the write operation, the description fully covers the required workflow (preview → confirm), mentions prerequisites, and references relevant siblings. The output schema exists, so no need to detail return values. Comprehensive for the tool's complexity.

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%, meaning the description text must compensate. It does: explains workout shape matches preview, clarifies confirmation_token's source, and details the confirm parameter (dev-only, no JWT secret). Adds meaning beyond the bare schema definitions.

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 explicitly states it creates a structured running workout in Garmin Connect library, with a clear verb-resource pair. It distinguishes from sibling tools like preview_running_workout (preview only) and schedule_workout (scheduling), and emphasizes that this is a WRITE operation.

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?

Provides explicit when-to-use guidance: requires writes enabled and a confirmation token from preview_running_workout, and explains how to get the workout onto the watch via schedule_workout. Clearly differentiates from preview and scheduling workflows.

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