icu_get_workouts_in_folder

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

Annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) already cover safety and behavior. The description adds that specific workout attributes are returned, which is useful but not critical. No additional behavioral traits like error handling or pagination are disclosed.

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 that efficiently conveys the tool's action, scope, and output fields, with no unnecessary words. It is well-structured and immediately readable.

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 the single, well-described parameter and existence of an output schema (presumably documenting return values), the description is sufficient. It mentions returned fields, covering key aspects. However, it could briefly note that it only lists workouts from a specified folder, not the folder metadata itself.

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 one parameter (folder_id) with a clear description ('Folder ID to get workouts from'), achieving 100% schema coverage. The tool description does not add further detail beyond what the schema provides, so baseline 3 is appropriate.

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 explicitly states the tool lists workouts from a specific folder or training plan, including the fields returned (name, type, structure, training load, intensity factor). This makes the purpose clear and distinguishes it from sibling tools like icu_get_workout_library or icu_get_upcoming_workouts.

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 mentions the tool operates on 'one specific library folder or training plan', implying when to use it, but does not explicitly state when not to use it or provide alternatives. Among many sibling tools, clearer guidance on selection would be beneficial.

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