delete_exercise_template

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Delete', which implies destructive action, but it does not disclose whether the deletion is irreversible, whether it affects exercises referencing the template, or if any permissions are required. This is a significant gap for a mutation tool.

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 a single sentence that is direct and front-loaded. It contains no unnecessary words and immediately communicates the core action and subject. Every word earns its place.

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 operation with one parameter and no output schema, the description provides the essential information needed to invoke the tool: what it deletes and how to identify the target. However, the lack of annotations and behavioral details (e.g., irreversibility, potential side effects) leaves the tool only minimally complete. It is adequate for basic usage but not robust.

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 has one parameter, exerciseTemplateId (string), with no description. The phrase 'by its id' clarifies that this parameter is the identifier of the exercise template, adding some meaning beyond the raw schema. However, it does not explain how to obtain the ID, whether it should be a UUID or any other format, or any validation rules. Given the schema coverage is 0%, the description partially compensates but not fully.

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'), the resource ('custom exercise template'), and the identifier ('by its id'). This distinguishes it from sibling tools like get_exercise_templates and create_exercise_template, which are read and create operations.

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 implies the tool should be used when a custom exercise template needs to be deleted, and that an ID is required. However, it does not explicitly state when to use it over alternatives, nor does it mention any prerequisites or exclusions. For example, it doesn't clarify whether this only works for user-created templates or if there are restrictions.

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