Garmin Activity Weather

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating safe read behavior. The description adds the nuance 'when available,' implying the tool may return no data for some activities. This is a useful addition but minimal beyond that. No contradictions with annotations.

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 description is a single sentence that immediately states the tool's purpose with a verb and resource. It is concise and front-loaded, with no extraneous information. Ideal structure for quick scanning.

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?

The tool has 4 parameters, an output schema, and several siblings. The description is minimal but covers the core functionality. It does not explain 'when available' in detail or how privacy_mode/response_format affect output, though these are in the schema. Adequate but with gaps.

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?

The description does not mention any parameters. Schema coverage is 75% (3 of 4 parameters have descriptions), so the schema already provides parameter meaning. Per guidelines, baseline is 3 when schema coverage is high, so this score is appropriate.

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 clearly states 'Get Garmin activity weather by activity id' with a specific verb and resource. It adds the qualifier 'when available,' indicating that weather data may not exist for all activities. However, it does not distinguish itself from similar sibling tools like garmin_get_activity or garmin_get_activity_details.

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 provides no guidance on when to use this tool versus alternatives. It does not mention contexts in which weather data is typically available (e.g., outdoor activities) or suggest checking other tools first. Given the many similar sibling tools, usage guidance is lacking.

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