tp_create_strength_workout

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

No annotations are provided, so the description carries full burden. It states the workout is created on the athlete's calendar and details the block structure, including types and constraints. It also notes that the athlete parameter is for coach accounts. It could mention potential side effects like overriding existing workouts, but overall is 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?

The description is two sentences that are front-loaded and efficient. Every sentence adds essential information: purpose, key components, and reference to related tool. No wasted words.

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?

With no output schema, the description lacks information on return values. However, for a creation tool, the input details are comprehensive. The sibling tools suggest a rich context, and this tool is well-specified despite the omission of output behavior.

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 100%, so baseline is 3. The description adds value by explaining the blocks structure, block types, and the requirement for superset/circuit blocks to have equal sets. It also lists possible set parameters, which is not in the schema properties descriptions.

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 creates a structured strength/gym workout on the athlete's calendar, using a specific verb ('Create') and resource. It distinguishes from sibling tools like tp_create_workout by specifying 'strength/gym workout' and referencing tp_search_exercises for blocks.

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 that exercises should come from tp_search_exercises, providing a clear preparatory step. However, it does not explicitly contrast with tp_create_workout or state when not to use this tool, leaving some ambiguity.

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