delete_workout

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly states the action is permanent ('Permanently removes'), which is important for a destructive operation. It could add more about side effects or failure behavior, but the core irreversibility is disclosed.

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 short and front-loaded with the purpose, followed by the permanent-deletion warning and parameter guidance. There is minor redundancy between 'Delete a workout' and 'Permanently removes a workout', but overall it is tight and well-organized.

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 single-parameter destructive tool, the description covers the essential context: what is deleted, permanence, and how to find the ID. An output schema exists, so return-value documentation is not required. It is slightly incomplete only in not addressing the plural delete_workouts alternative.

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 description coverage is 0%, so the description must compensate. It does: 'workout_id: ID of the workout to delete (get IDs from get_workouts)' adds real meaning beyond the schema's bare integer type and tells the agent where to source valid IDs.

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 ('Delete' / 'Permanently removes') and the resource ('workout from your Garmin Connect workout library'). It is specific about operating on a single workout, though it does not explicitly contrast itself with the sibling delete_workouts (plural).

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?

The description gives clear context by telling the agent to obtain workout IDs from get_workouts, which is the natural workflow prerequisite. It does not explicitly discuss when not to use this tool or compare it to delete_workouts, but the usage path is reasonably clear.

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