garmin_get_activity_detail

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

Annotations indicate readOnlyHint=true, and description consistently presents a read operation. Adds detail about what the 'detailed' mode returns (lap splits, HR-zone breakdown) beyond annotations. Could mention rate limits or auth, but overall transparent.

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?

Highly concise: a single sentence that front-loads the main purpose, lists key metrics, and provides actionable instruction. No filler.

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 output schema exists, description doesn't need to detail return values. It covers all necessary context: what data is retrieved, the two modes, and prerequisite. Complete for this tool.

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%, baseline 3. Description adds meaning by elaborating on response_format values: 'concise' vs 'detailed' with specific added data. This goes beyond the schema's simple enum description.

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?

Description starts with 'Deep-dive a single Garmin activity' and lists specific metrics (distance, time, HR, etc.), clearly stating the tool's purpose. It distinguishes itself from siblings by mentioning how to get the activity_id from garmin_list_activities.

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?

Explicitly instructs to get activity_id from garmin_list_activities first, providing a prerequisite. Explains the two response_format options ('concise' vs 'detailed'). Does not explicitly state when not to use, but the context is clear given sibling tools.

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