Delete Workout

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

Annotations include destructiveHint: true and openWorldHint: trueable. The description adds nothing beyond what the annotation already conveys—it just says delete. It doesn't mention irreversibility, scope (e.g., does it affect scheduled instances?), or other side effects. With annotations present, the bar is lower, but the description provides no additional behavioral context.

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?

Extremely concise, one sentence. No fluff. Could add more info but structure is efficient.

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 simple delete with one parameter, the description covers the action but lacks details on effects (e.g., if it also removes scheduled occurrences, auth needed). With destructiveHint present, some context is implicit, but no extra info.

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 covers the only parameter with a description (`workoutId` - 'The unique workout identifier (required)'). The description adds nothing about the parameter. Baseline 3 is appropriate since schema already documents it.

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 is concise and specific: 'Delete a workout from Garmin Connect.' It clearly identifies the verb (delete) and the resource (workout), and differentiates from sibling tools like delete_activity or delete_gear_collection, which target other entities.

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?

No guidance is given on when to use this vs. alternatives like unschedule_workout or update_workout. The description simply states the action without any context about prerequisites, consequences, or alternative tools for when a workout should be removed from a schedule rather than permanently deleted.

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