garmin_scheduled_workouts

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

Annotations already indicate readOnlyHint=true, and the description's 'List' aligns with that. The description adds the default-to-current-month behavior, which is useful context, but does not disclose return format, pagination, or other behavioral details. With annotations covering safety, the added value is moderate.

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, concise sentence with no fluff. The key information (action, resource, scope, default) is front-loaded, making it easy to parse quickly.

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?

With no output schema, the description should clarify what data is returned (e.g., workout details, dates), but it does not. It also lacks guidance on edge cases like invalid months or empty results. For a simple list tool, it is adequate but missing details that an agent would need to interpret the response.

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%, so the description must compensate. It mentions 'given month' and default behavior but fails to specify the expected integer ranges (e.g., month 1-12, year format) or any parameter constraints. The description is too vague to guide correct parameter construction.

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 a clear action ('List') and resource ('workouts scheduled in a given month'), making the tool's purpose obvious. It distinguishes from siblings like garmin_list_workouts by scoping to scheduled workouts and a specific month, though it doesn't explicitly name alternatives.

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 implies usage (when you need scheduled workouts for a month) but provides no explicit guidance on when not to use it or how it compares to siblings like garmin_list_workouts or garmin_schedule_workout. It lacks exclusion criteria or alternative routing.

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