delete_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 explicitly discloses that deletion is permanent, which is the critical behavioral warning for a destructive operation. It does not mention side effects on scheduled workouts, but the permanence statement is valuable and non-obvious.

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 compact and front-loaded: the main action, the permanent effect, and the only parameter are stated in three short sections. There is no filler or redundant information.

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 tool, the description is mostly adequate for invoking it correctly. However, it omits important context about the sibling delete_workouts, whether deleting also unschedules workouts, and any authorization requirements. The output schema presence makes missing return-value details 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?

The schema only defines workout_id as an integer with 0% description coverage. The description compensates by explaining the parameter's role and pointing to get_workouts as the source of valid IDs, which is actionable guidance beyond the schema field name.

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?

Clearly identifies the action as deleting a single workout from Garmin Connect and emphasizes that the removal is permanent. It does not explicitly contrast with the sibling delete_workouts, but the singular wording and single workout_id make the scope reasonably clear.

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 a useful prerequisite by directing the agent to get IDs from get_workouts. However, it does not mention when to prefer this tool over delete_workouts or unschedule_workout, nor does it explain scenarios where deletion may be inappropriate.

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