upload_course

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly states that this uploads a GPX file into a Garmin Connect Course and describes post-upload usage, but it does not disclose side effects such as duplicate handling, overwrite behavior, required authentication, or validation rules.

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 purpose is front-loaded in the first sentence, followed by a compact and useful operational context paragraph, then a clearly structured Args block. Every line adds information; there is no filler or repetition of the schema titles.

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 that an output schema exists and all input parameters are thoroughly documented, the description is complete enough for normal invocation. The only gaps are explicit failure-mode behavior and routing guidance relative to sibling tools, which are minor in the context of the other rich details provided.

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 schema has 0% description coverage, but the Args section fully compensates: gpx_path is defined as an absolute path, course_name's override behavior and default are explained, the full allowed set of activity_type values is listed, and description's purpose is clarified. This goes well beyond what the schema provides.

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 opens with a specific verb and resource: 'Upload a GPX file as a Garmin Connect Course.' It also explains the purpose of the resulting course (navigation, PacePro), which clearly differentiates it from sibling tools like download_course_gpx and delete_course.

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 practical context about loading the course onto a watch, which implies when this tool is useful, but it does not explicitly mention alternatives or when not to use it. An agent can infer the use case but is not directly routed away from related tools like upload_workout.

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