hevy_create_exercise_template

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

No annotations are provided, so the description fully carries the burden. It discloses the dry-run default, the requirement for a server env variable to actually create, and the expected response shape, ensuring the agent understands the tool's non-obvious behavior.

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 dense but well-structured, front-loading the action and then detailing enums and special behavior. It could be slightly more concise, but every sentence adds value.

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 the nested object, multiple enums, and dry-run behavior, the description is thorough. It covers all essential aspects for correct invocation without relying on an output schema.

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?

Although schema description coverage is 0%, the description enumerates all enums (exercise_type, muscle_group, equipment_category) and explains the exercise object structure, including the optional other_muscles array, providing complete parameter semantics beyond the raw 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 the action 'Create a custom exercise template' and lists required fields (title, exercise_type, muscle_group, equipment_category), distinguishing it from sibling tools like hevy_list_exercise_templates and hevy_search_exercise_templates.

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?

It explicitly explains the dry-run default behavior and the environment variable (HEVY_MCP_ALLOW_WRITES=1) needed to execute actual writes, providing clear when-to-use and how-to-enable guidance.

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