unschedule_workout

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states the deletion does not remove the underlying workout template, that the workout remains in the library and can be re-scheduled, and that the listing is eventually consistent. This gives an agent a clear picture of side effects and timing behavior.

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?

Every sentence adds value: the operation, the non-destructive side effect, the critical id provenance warning, the eventual-consistency note, and the parameter explanation. The most important caveat is surfaced early with 'IMPORTANT', and the structure is easy to scan.

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 single-parameter mutation tool with an output schema, the description provides all necessary context: what the operation does, what it does not do, where to get the correct id, and a timing caveat. Nothing essential for correct invocation is missing.

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 coverage is 0%, and the schema only shows an integer named scheduled_workout_id. The description compensates fully by defining it as the calendar-entry id, distinguishing it from the workout's own id, and directing the agent to get it from a specific source field in get_scheduled_workouts.

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: 'Remove a scheduled workout from the Garmin Connect calendar' and clarifies it deletes only the calendar entry, not the workout template. This distinguishes it from related tools like schedule_workout, get_scheduled_workouts, and delete_workout.

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 guidance on where to obtain the required id — from get_scheduled_workouts, not get_workouts — and warns about eventual consistency after scheduling. It does not explicitly contrast with the plural sibling unschedule_workouts, but the singular/plural distinction is reasonably clear from the name.

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