get_enduraw_race_gpx

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about read-only semantics, permissions/auth, behavior for an unknown race name, or expected payload size even though a "complete GeoJSON track" is likely a large response. The one genuinely useful disclosure is the contents/shape of the return value, but that is closer to a result summary than a behavioral trait.

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?

One dense sentence with the resource and its returned contents front-loaded and no filler. The capitalization of ALL and the parenthetical field list are efficient emphasis rather than padding, though the sentence could have used the freed space for usage guidance.

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 and no annotations, the description does the essential job of stating what comes back (track coordinates plus all checkpoints with distance, altitude, D+). It is adequate for a one-parameter read tool, with the only real gap being error/empty-result behavior and payload size expectations.

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% and the single race_name parameter already carries an examples-based description, so the schema does the heavy lifting. The description adds only the mild implication that the identifier is a race and that the response is per-race; nothing about name-matching, aliases, or failure on ambiguity is provided.

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 pairs a specific verb ("Retrieves") with a precise resource ("complete GeoJSON track coordinates and ALL official checkpoints / aid stations") for a race. It goes beyond the name by enumerating the returned fields (distance, altitude, cumulative D+), which lets an agent distinguish it from analysis-oriented siblings like get_enduraw_race_course_profile, though it never explicitly names that sibling.

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?

Usage is only implied: the phrase "for a race" signals this is the raw course/track fetch rather than an analysis. There is no explicit when-to-use statement, no guidance on choosing it over get_enduraw_race_course_profile or get_enduraw_races, and no exclusions or prerequisites.

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