add_exercises_to_session

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly states the operation is an add operation, that ordering matters, and that the tool returns created workout sets with full exercise details. It doesn't discuss error conditions or ipotential side effects, but the disclosed behavior is substantive and goes beyond the schema.

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 three concise sentences. It front-loads the core purpose, then gives a parameter-specific instruction, then describes the return value. Every sentence adds value with no redundancy or filler.

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 2-parameter mutation tool with no annotations or output schema, the description covers the operation, parameter guidance for exercise_ids, and return behavior. It omits explicit mention that the session must already exist, but this is a minor gap given the sibling context and the meaning of 'Add exercises to a personal workout session'.

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%, so the description must compensate. It adds meaningful semantics for exercise_ids ('ordered list' and 'use get_exercise_library to look up IDs'). However, workout_id is left unexplained; its meaning is mostly inferred from the tool name and description, so the compensation is incomplete.

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 a specific action ('Add exercises') on a specific resource ('personal workout session'), and explicitly notes the 'in order' behavior. This distinguishes it from sibling tools like create_personal_session (creating sessions) and get_exercise_library (looking up exercises).

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 provides clear context for when to use the tool (adding exercises to an existing personal workout session) and explicitly directs users to get_exercise_library for ID lookup. However, it does not explicitly state when not to use it or mention the alternative of creating a session first with create_personal_session.

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