get_enduraw_activities_map

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

With no annotations, the description carries the full behavioral burden. It discloses global scope and returned data types, implying a read-only bulk geospatial retrieval, but it does not mention whether results are paginated, how large the response may be, permission requirements, or performance considerations for global activity 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?

The definition is a single front-loaded sentence that efficiently states the operation, returned data, and broad scope. The parenthetical use-case note is helpful and not wasteful, though the phrase 'across the globe' is slightly redundant with 'geolocation'.

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?

For a one-parameter read tool with no output schema, the description is reasonably complete: it identifies the core returned geospatial fields and the global scope of activities. It could be stronger by clarifying how the period parameter affects results and how this map-oriented view relates to sibling activity tools.

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 description coverage is 100%, and the single period parameter is fully documented in the schema with its default and allowed values. The description does not add any parameter-specific meaning such as how period affects returned routes or coordinates, so the schema does the work.

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 names a specific fetch operation and enumerates the geospatial outputs: GPS coordinates, start points, and session routes for all recorded activities. This distinguishes it from sibling activity-list or analysis tools by emphasizing map/geographic data, though it does not explicitly name the siblings it differs from.

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 parenthetical says it is used in the Enduraw Heatmap and geographic explorer, which implies visualization or map-based use cases. However, it gives no explicit guidance on when to call this instead of get_enduraw_activities, get_enduraw_race_gpx, or activity-specific tools, and offers 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.