Get Hevy Exercise Template

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered. The description's one added behavioral detail is that muscle classifications come back with the template, which is modest but real return-content context beyond the annotations. It says nothing about what happens if the exercise_id does not exist.

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?

A single tight sentence with the resource and the key extra detail front-loaded; there is no filler. It is arguably too terse rather than verbose, but nothing present is wasted.

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 the return shape need not be described, and the annotations cover safety. However, for a lookup tool whose only input is an undocumented id, the description leaves the caller without guidance on sourcing or validity of exercise_id.

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%: exercise_id is typed only as a string with no format, source, or example. The description implies the parameter identifies a single template but never says where such an id comes from (for example, list_hevy_exercise_templates or search_exercises) or what a valid id looks like.

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?

"Get one Hevy exercise template" states a specific verb and resource with explicit singular scope, and adds that muscle classifications are included. An agent can distinguish it from list_hevy_exercise_templates by the word "one," though no sibling is named directly.

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?

There is no explicit when-to-use statement, no prerequisites, and no named alternatives. The singular "one" hints at a fetch-by-id versus list distinction, but the agent must infer that from the wording rather than being told.

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