garmin_activity_workouts

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so 'Changes nothing' merely restates structured metadata and adds no new information. Nothing is said about behavior when an activity has no associated workout (empty result vs. error) or about any retrieval constraints, leaving the behavioral picture thin.

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?

Two short sentences, front-loaded with the core action, with no filler text. The second sentence is largely redundant against the annotations, which slightly reduces the value of the phrasing but not its brevity.

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 an output schema present, return values need no explanation, and the single simple parameter plus rich annotations mean little else is required. The only real gap is the absence of any note on the no-workout case or linkage to sibling activity tools.

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% for the single activity_id parameter, so the schema offers only a type and bounds. The description partially compensates by framing the parameter as an identifier for a 'recorded activity,' but it adds no detail on format, source, or validity beyond that.

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?

States a specific verb and resource: 'Read structured workout steps associated with a recorded activity.' This clearly distinguishes it from generic siblings like garmin_activity or garmin_activities, which cover activity data rather than workout steps. It stops short of naming a sibling alternative, but the resource is specific enough to route correctly.

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?

Usage is only implied: an agent can infer it should call this when it needs the structured workout steps for a known activity_id. There is no explicit when-to-use or when-not-to-use guidance, and no mention of how it relates to garmin_activity, which is the nearest alternative.

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