delete_workouts

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly labels the operation as permanent removal, which is essential for a destructive tool, and notes the batch nature of the call. It does not discuss failure behavior or permissions, but the core destructive consequence 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 front-loaded with the key purpose, then adds the permanence warning and a compact Args explanation. No extraneous content.

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 one-parameter deletion tool, the description plus schema covers the action, the permanent effect, and the ID source. An output schema exists, so return-value details are not required. It could still mention the singular delete_workout alternative or what happens with invalid IDs, but nothing critical 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%, so the description compensates by explaining that workout_ids is a list of workout IDs and pointing to get_workouts as the source. This is sufficient for the only parameter.

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 action and resource: deleting multiple workouts from Garmin Connect and permanently removing them from the workout library. The word 'multiple' and 'single call' distinguish it from the sibling delete_workout, which appears to handle a single 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?

The description makes clear this is for deleting multiple workout IDs at once and tells the agent to obtain IDs from get_workouts. It does not explicitly mention when to use the singular delete_workout instead, so there is a small exclusion gap.

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