Delete strength workout

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

Annotations already declare destructiveHint=true and readOnlyHint=false, which the description does not contradict. The description adds no additional behavioral context such as irreversibility, associated data deletion, or permission requirements, but given the annotation coverage, it provides adequate 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?

The description is a single sentence that is direct and to the point, containing no fluff or redundant information. It fully communicates the essential action and target.

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 two parameters and no output schema, the description, combined with the annotations and schema, provides sufficient context. No critical details about side effects or return values are required, and the tool is easy to invoke correctly.

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 input schema has 100% parameter coverage, documenting both 'athlete' and 'workout_id'. The description's phrase 'by ID' aligns with the required workout_id parameter but does not add new meaning beyond the schema, so it meets the baseline for high schema coverage.

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 ('strength workout') with the identifying method ('by ID'). This clearly distinguishes it from sibling tools like tp_delete_workout, which targets general workouts, and other delete tools for different entities.

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 use for deleting strength workouts, but it does not explicitly state when to use this tool instead of tp_delete_workout or other alternatives. The presence of a sibling tool for regular workout deletion suggests a need for such guidance, so the usage context is only implied rather than stated.

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