volume_by_muscle_group

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

Discloses volume calculation, warmups excluded, and caching behavior. Without annotations, this is helpful. Could add more on pagination or performance for large windows.

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 concise sentences, front-loaded with core function, then use case and details. No redundancy or extra words.

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?

Covers main purpose and important behavioral details, but lacks parameter documentation and output explanation (though output schema may supplement).

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 coverage is 0%, but description does not explain parameters since, until, max_pages. Only says 'over a window' without format or default behavior. Missing crucial info for correct use.

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?

Clearly states it aggregates volume by muscle group, defines volume formula, and gives a specific use case. Distinguishes from siblings like list_workouts and progression_trend.

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?

Explicitly mentions useful prompt ('which muscle groups neglected?') and prerequisite (template list loaded). Could clarify when not to use or alternatives.

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