remove_exercise

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

With no annotations, the description carries the full behavioral burden and does disclose a meaningful side effect: an emptied block is also removed. However, it omits permissions/auth requirements, irreversibility, response behavior, and what happens to the remaining exercises in the session. This is useful partial transparency, not complete disclosure.

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 definition is a single tight sentence with no filler. The core action is front-loaded, and the cascade caveat is included only because it materially affects behavior.

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 mutation tool with no annotations, no output schema, and zero schema description coverage, the description is too thin. It covers purpose and the empty-block cascade but leaves parameter meanings, authorization context, and return/error behavior unspecified.

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 description coverage is 0% across three parameters, so the schema provides bare names and types only. The description does not explain program_workout_id, workout_set_exercise_id, or team_id, nor how they relate to the session/exercise removal. It adds almost no parameter meaning beyond the schema.

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: removing one exercise from a session. It also clarifies the cascade scope, making it distinguishable from remove_block or delete_session by the exercise-level resource. It does not explicitly name alternatives, which keeps it from a 5.

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 explains what the tool does but gives no guidance on when to use it versus remove_block, delete_session, or update_session. It lacks prerequisites, exclusions, or any when-not conditions.

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