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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond them: the post-uncertain-creation verification scenario and the requirement to surface every serviceAnnouncements message from Geekist distinctly, which is non-obvious response-handling behavior an agent would otherwise skip. Remaining gaps (behavior when the ID is unknown, error semantics) are minor for a read-only tool.

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 sentences with the primary operation front-loaded and the response-handling obligation placed afterward; nothing is redundant. The second sentence is a bit of an operational addendum rather than tightening the tool's purpose, keeping it from a 5.

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?

For a simple one-parameter read tool with annotations present and no output schema, the description covers purpose and the announcements-handling requirement. It does not indicate what the workout payload contains or what happens when the ID doesn't resolve, leaving some gaps for an agent relying solely on this text.

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 single workoutId parameter is only explained by the schema's numeric pattern. The description clarifies that it is a Garmin Connect workout identifier, which compensates partially, but adds no detail on ID sourcing or format expectations.

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 names a specific verb and resource ('Read a workout saved in Garmin Connect') plus the lookup key ('by its workout ID'), which is far more than the tautological name restatement. It stops short of explicitly contrasting with garmin_get_activity_workouts or garmin_preview_workout, so sibling differentiation is only implicit.

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?

'Including after an uncertain creation' implies a verification/recovery use case following garmin_create_workout, which is useful contextual guidance. However, no alternative tool is named and no when-not-to-use condition (e.g., for listing workouts) is given, so the agent must infer selection.

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