add_exercise

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

With no annotations, the description carries the burden. It discloses the end condition constraint (set reps OR duration OR neither) and recommends list_exercises. However, it omits behavioral traits like whether it validates exercise names, modifies a workout in progress, or requires a prior create_workout. The disclosure is partial.

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 brief and well-structured: a one-line purpose, a clarifying sentence on end condition, then bullet-pointed args. Every sentence adds value; no redundancy. Perfectly sized for quick comprehension.

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?

Parameter details are complete, and an output schema exists (so return values need not be explained). However, the description misses workflow context: it does not mention that a workout must be created first (via create_workout) or that this step is added to a current workout. This gap could mislead an agent into calling add_exercise without a workout 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?

Schema coverage is 0%, so description compensates fully. It explains each parameter: exercise (name, examples, list_exercises), duration (format 'M:SS' or 'lap'), reps (integer), weight (lbs), notes (display text). This adds significant meaning beyond field types and defaults.

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 tool adds a strength/cardio exercise step, specifying the verb 'add' and resource 'exercise step'. It distinguishes from sibling tools like add_bike or add_run through the 'strength/cardio' qualifier, though not explicitly naming alternatives.

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 usage for adding exercise steps with an end condition, but does not explicitly state when to use this tool over siblings like add_bike or add_run. The mention of list_exercises provides a hint for pre-usage, but no when-not-to scenarios or alternative guidance.

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