unschedule_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 discloses the side effect of not deleting the template and warns about the eventual-consistency delay. It does not mention error behavior, idempotency, or permissions, which would be useful but are not essential for basic operation.

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 description is somewhat lengthy due to the important notes, but each sentence adds value. The use of 'IMPORTANT' and 'Note' labels makes it well-structured and easy to parse.

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 that an output schema exists, the description need not explain return values. The tool is simple with one parameter, and the description covers purpose, parameter semantics, side effects, and timing, providing all necessary context for an agent to decide when and how to invoke it.

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?

The schema only provides type integer with zero description coverage. The description fully compensates by explaining that the parameter is the calendar-entry ID, distinct from the workout ID, and precisely specifies where to obtain it (from get_scheduled_workouts' scheduled_workout_id field).

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 ('Remove a scheduled workout from the Garmin Connect calendar') and distinguishes it from deleting the underlying template, making the tool's purpose unambiguous.

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?

It explicitly describes the use case and clarifies that this operation preserves the workout template, implying when to use this over a full deletion. The note about eventual consistency provides timing guidance. However, it does not name alternative sibling tools explicitly, but the context is clear enough.

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