upload_course

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

No annotations are provided, so the description carries the full transparency burden. It discloses the core state change (uploading/creating a course in Garmin Connect) and downstream usage, but it does not mention permissions, duplicate handling, overwrite behavior, or failure conditions. This leaves some important behavioral aspects undisclosed.

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 compact and front-loaded: the action is stated in the first sentence, followed by one useful contextual sentence and a clean parameter list. Every part earns its place, and there is no repetition of information already visible in the schema.

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's complexity is well covered: purpose, parameter semantics, defaults, accepted values, and downstream use cases are all present, and an output schema exists so return values do not need to be described. The remaining gaps are explicit alternative routing and deeper behavioral caveats, which prevent a perfect score.

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?

With 0% schema description coverage, the Args block fully compensates. It defines gpx_path as an absolute path, explains course_name's default behavior, enumerates valid activity_type values, and clarifies that description is optional. This is substantial added meaning beyond what the bare input 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 opening line 'Upload a GPX file as a Garmin Connect Course' names a specific action and resource, making the tool's core function immediately clear. The additional context about loading the course onto a watch for navigation or PacePro further disambiguates it from workout upload siblings like upload_workout and upload_workouts.

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 clear context: use this tool when a GPX file needs to become a Garmin Connect Course for navigation or PacePro strategy. It does not explicitly name alternatives or state when not to use it, so the agent has to infer the distinction from the word 'Course' versus the workout-uploading sibling tools.

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