Delete a saved workout

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

Annotations already declare destructiveHint=true and readOnlyHint=false, covering the destructive nature. The description adds the specific behavioral scoping to plans vs. activities, which is valuable context beyond the annotations. No contradiction with annotations.

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 only two sentences, front-loaded with the action and key constraint. Every sentence adds necessary information, with no redundant phrasing.

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 tool with one parameter and an output schema, the description covers the main behavioral nuance (plans only). However, it does not clarify how to obtain the workout_id or differentiate plan IDs from activity IDs, which may require cross-referencing sibling tools like garmin_list_workouts. This is a minor gap, keeping it from a perfect score.

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?

With 0% schema description coverage, the description should compensate by explaining the parameter. It does not mention workout_id at all, leaving the agent to infer its meaning from the tool name and title. The parameter name is self-explanatory, but the description fails to explicitly state that workout_id refers to a plan ID, not an activity ID, which is a notable gap.

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 uses a specific verb ('Delete') and resource ('saved workout'), and clarifies scope ('Only affects plans — recorded activities cannot be deleted'). This clearly differentiates from related siblings like garmin_unschedule_workout (unscheduling) and activity-related tools.

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 explicitly states the tool only affects plans, not recorded activities, giving a clear boundary on when to use it. While it doesn't name alternatives or exclusion conditions, the distinction between plans and activities is the key usage constraint and is well-communicated.

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