list_hevy_routines

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

The description only says 'list,' implying a read operation, but no annotations are provided. It fails to disclose any behavioral traits such as pagination behavior, rate limits, or ordering. The description does not add value beyond the tool name.

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 very concise (one sentence), but it is under-specified. It lacks necessary details that would help an agent use the tool correctly. Conciseness should not sacrifice usefulness.

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?

Despite having an output schema (unknown structure) and simple parameters, the description is incomplete. It does not explain what a Hevy routine is, how pagination works, or any context about the data returned. The tool definition is minimal and insufficient for effective use.

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?

The input schema has two parameters (page, page_size) with no description coverage (0%). The description does not explain these parameters, their defaults, or how they affect the listing. The agent cannot determine the meaning or usage from the description alone.

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 states 'List Hevy routines,' which is a verb+resource pair, but it is very generic and does not differentiate from sibling tools like list_hevy_workouts or list_hevy_routine_folders. The agent would need additional context to know exactly what a 'routine' is in this domain.

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 guidance on when to use this tool versus alternatives. Given the presence of multiple similar sibling tools (e.g., list_hevy_workouts, list_hevy_routine_folders), the description should provide context for when listing routines is appropriate.

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