delete_garmin_workout

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

Even though destructiveHint is already set, the description adds important behavioral context: the operation is irreversible, there is no undo or trash, and it returns an authentication prompt instead of throwing an error when no session exists. These details go beyond the annotation and meaningfully inform agent 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?

The description is three sentences with no filler. The core action is front-loaded, followed by the irreversibility warning and the necessary preconditions/fallback behavior. Every sentence earns its place.

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 one-parameter destructive tool with no output schema, the description covers the purpose, the irreversible side effect, the recommended confirmation step, and the authentication failure behavior. Nothing critical is missing for an agent to invoke it correctly.

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 single parameter workoutId is fully documented in the schema with its type and origin. The description mainly reinforces using the right ID by listing sources, but does not need to add more because schema coverage is 100%.

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 states a specific verb ('Permanently delete'), a specific resource ('workout from Garmin Connect'), and the key identifier ('by workoutId'). It is clearly distinguishable from sibling tools like update_garmin_workout or schedule_garmin_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?

It explicitly instructs the agent to use list_garmin_workouts or get_garmin_workout first to confirm the workoutId, which is actionable pre-use guidance. It also explains what happens when no valid session exists and directs the agent to authenticate_garmin, covering the main failure path.

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