Create Hevy Exercise Template

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds genuinely useful behavior — dry_run=true is a preview and only dry_run=false persists to Hevy — but says nothing about duplicates, idempotency, or what a preview returns.

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?

Three short sentences, front-loaded with the purpose followed by the dry_run mechanism and the safety rule. Nothing is wasted, though the third sentence slightly restates the intent of the second.

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?

An output schema exists, so return values need not be described, and the description covers the key decision (preview vs commit). For a create tool with a nested required object it would be stronger if it noted conflict/duplicate behavior or prerequisites, but it is adequate overall.

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, and it does for dry_run by explaining preview vs write. However, the required nested exercise object (title, exercise_type, equipment_category, muscle_group, other_muscles) is left entirely to the schema's enums, with no added meaning about how those fields are used or validated.

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?

"Preview or create a custom Hevy exercise" names a specific verb (create) plus resource (exercise template) and adds the preview mode, so an agent can tell it apart from the sibling get/list tools. It stops short of explicitly naming which sibling to use when the agent instead wants to search or read existing 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 states the write gate plainly: "Only execute a write when the user has requested it," and explains that dry_run defaults to preview. That is clear when-to-write guidance, but it offers no exclusions or alternatives (e.g. use search_exercises to check for an existing template first).

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