Get a Garmin activity

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description goes further by disclosing the full breadth of returned content, including strength-specific set/rep/weight data. It stops short of covering edge cases like missing data, unit conventions, or auth failures, which keeps it from a 5.

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 key statement is front-loaded, and the long field enumeration is functional rather than decorative since it determines whether the tool fits the agent's data need. The list is dense but every clause names a distinct data category; minor tightening would only marginally improve it.

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 carries the burden of describing returns and does so thoroughly, including the conditional strength-activity fields that would otherwise be invisible. An agent can decide correctly whether to call it and how to obtain its argument.

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 100% for the single activity_id parameter, so the baseline is 3. The description adds real value beyond that by naming the two tools that produce a valid id, which the schema does not say.

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?

Opens with a specific verb and resource ("Full summary of one Garmin activity") and then enumerates the exact fields returned, so an agent knows precisely what data this tool surfaces. It explicitly distinguishes itself from garmin_get_activity_laps and from the search/day tools that locate ids.

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?

Gives explicit routing in both directions: per-lap rows belong to garmin_get_activity_laps, and the required activity_id is obtained via garmin_search_activities or garmin_get_day. That is a when-to-use plus how-to-prepare instruction, leaving nothing to inference.

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