hevy_get_routine

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

No annotations are provided, so the description must disclose behavior. It only states the action without addressing side effects, read-only nature, error behavior (e.g., if routine not found), or authentication requirements. For a single-resource fetch, read-only is implied but not explicit.

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 a single sentence with no filler. However, it is overly sparse; while concise, it sacrifices useful detail. It is front-loaded with the core action but lacks elaboration.

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 no output schema and no annotations, the description is insufficiently complete. It does not describe the return format, possible errors, or any additional behavior. For a simple GET endpoint, it is acceptable but minimal.

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 parameter descriptions are 0% covered. The description adds that the routine is identified by UUID, but the schema already specifies format=uuid. It does not explain the purpose of 'routineId' beyond the tool name, nor does it compensate for missing schema 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 'Fetch one routine by UUID' specifically names the action (fetch), resource (one routine), and identifier (UUID). It clearly distinguishes from sibling tools like 'hevy_list_routines' which fetches all routines.

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?

No guidance on when to use this tool versus alternatives (e.g., when to use 'hevy_list_routines' or 'hevy_get_routine_folder'). It does not specify prerequisites or context such as needing the UUID from a previous list call.

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