create_workout_plan

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

No annotations provided, so description carries full burden. It discloses the confirm-gated preview/execute behavior, default section for exercises, and valid enum values. Could add whether it overwrites existing plans, but overall transparent.

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?

Description is a single sentence with inline details, front-loading the confirm-gate. Could be more structured (e.g., separate lines for key behaviors), but not overly verbose.

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?

Given 8 parameters and no output schema, description covers confirm behavior, exercise structure, section, and days. Missing some details (e.g., endDate behavior), but adequate for a creation tool.

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 low (25%). Description adds significant meaning: structure of exercises array, section enum with defaults, and optional days. It compensates well for the sparse 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 clearly states 'Create a workout plan for a client (confirm-gated)', which is a specific verb and resource. It distinguishes from siblings like create_diet_plan by focusing on workout plans.

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 the confirm-gated behavior ('Must be true to actually execute. If false/omitted, returns a preview only.'). However, it does not explicitly state when to use this tool versus alternatives like create_diet_plan or create_habit.

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