download_activity_kml

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly states that the tool saves the KML file to disk and returns the file path, which is a key behavioral trait. It does not mention overwrite behavior or error cases, but the core side effect and return contract are disclosed.

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?

Three short sentences, each earning its place: the action, the side effect/return value, and the practical use case. The description is front-loaded with the core purpose and contains no filler.

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 simple one-parameter download tool with an output schema, the description covers the main invocation needs: what is downloaded, what happens, and what is returned. The main gap is the lack of guidance on choosing this format over siblings, but the tool's simplicity keeps this impact modest.

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 0%, so the description must compensate for the parameter. It only says the file is for 'a specific activity,' which adds little beyond the parameter name 'activity_id.' It does not explain where to find the activity ID, its format, or how it relates to other activity tools.

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 clearly states a specific action ('Download a KML file') and the target resource ('a specific activity'). It does not explicitly name sibling format tools, but the KML resource is unambiguous from both description and tool name.

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?

There is no guidance about when to choose KML over the sibling formats (fit, gpx, tcx, csv). The note that KML can be opened in Google Earth hints at a use case, but there is no explicit when-to-use or when-not-to-use guidance.

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