get_activity_weather

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so 'read-only' simply repeats structured data. The remaining sentence about date format is misleading because the only parameter is activity_id — there is no date argument — and nothing explains what weather fields are returned, units, or behavior when an activity has no weather data.

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?

It is short and front-loads the verb+resource, which is good, but the parenthetical does not earn its place: 'read-only' duplicates the annotations and the date-format rule applies to no parameter. The brevity is under-specification rather than efficient density.

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?

An output schema exists, so return values need not be documented, but for a one-parameter tool with zero schema coverage the description should at least clarify the identifier and the meaning of 'activity weather'. As written, an agent cannot confidently tell what this returns or how to supply activity_id.

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 single parameter has 0% schema description coverage, so the description must explain activity_id but instead only mentions a YYYY-MM-DD date format that does not correspond to any parameter. It also does not clarify that activity_id accepts either an integer or a string, which the anyOf schema leaves ambiguous.

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 says 'Return activity weather', which gives a verb and a resource but leaves 'activity weather' ambiguous — it could be weather recorded during a workout or weather conditions forecast for an activity date. It does not distinguish this from the many other get_activity_* siblings such as get_activity_details or get_activity_splits.

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?

No indication of when to call this versus the ~60 sibling tools, no prerequisites, and no exclusions. The only context offered is the source system (Garmin Connect) and a read-only note, which do not help an agent choose between tools.

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