Delete Workout Template

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

With no annotations, the description carries the behavioral disclosure burden. It clearly states what gets destroyed (template and exercise slots) and what is preserved (history/sessions). It does not mention response/confirmation or irreversibility, but the word 'Deletes' plus the scope statement provides solid transparency.

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?

Two sentences with no filler: the first states the action and scope, the second states the key exclusion. The most important behavior is front-loaded.

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 one-parameter delete tool with no output schema, the description covers the action, the affected data, and the preserved data. An agent can call it correctly without needing additional context.

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?

The schema already documents the single parameter at 100% coverage, so baseline is 3. The description adds meaningful semantics by explaining that the name is fuzzy-matched while ids are exact, which clarifies how the 'template' string is interpreted.

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 opens with a specific verb and resource: 'Deletes a workout template and its exercise slots'. It also states the matching mechanism (fuzzy by name or exact by id), which makes it distinguishable from sibling deletion tools like delete_exercise and delete_nutrition_plan.

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 for the deletion scope and explicitly says it does not delete workout history/sessions, which helps the agent decide when not to use it. It does not name alternatives such as delete_exercise, but the resource distinction is enough for most routing.

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