delete_workouts

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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly states 'Permanently removes,' which communicates that the operation is destructive and irreversible. It does not mention permission requirements or partial-failure behavior, but the core destructive nature is clearly 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 compact and front-loaded: the first sentence states the action and scope, the second adds the key permanence detail, and the Args section gives exactly the needed parameter guidance. Every sentence contributes value without unnecessary elaboration.

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 destructive tool with an output schema, the description is complete: it covers what the tool does, that deletion is permanent, and how to source the IDs. No critical operational detail needed to invoke the tool correctly 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 must add meaning to the parameter. It does: 'workout_ids: List of workout IDs to delete (get IDs from get_workouts)' explains the parameter's purpose and provides the workflow for obtaining valid values. This goes beyond the bare schema definition of an integer array.

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 and resource: 'Delete multiple workouts from Garmin Connect in a single call' and reinforces it with 'Permanently removes multiple workouts from your Garmin Connect workout library.' It clearly distinguishes itself from the singular sibling delete_workout by emphasizing batch deletion.

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 usage context: use this tool to remove multiple workouts at once, and it tells the agent where to obtain the required IDs ('get IDs from get_workouts'). It does not explicitly call out the singular alternative delete_workout for when-only-one-deletion-is-needed, so it stops short of full when/when-not guidance.

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