export_activity_file

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

There are no annotations, so the description must carry the behavioral burden. It usefully discloses the key side effect that an earlier export of the same Activity is overwritten and that the tool returns the file's absolute path, though it does not mention permissions, error conditions, or the exact export folder location.

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 a single, front-loaded sentence that covers purpose, format options, overwrite behavior, and return value. It is dense but efficient, with no filler sentences.

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 two-parameter tool with full schema coverage and no output schema, the description is complete enough: it explains what is saved, the format choices, the overwrite behavior, and the returned absolute path. Missing details such as permissions or exact folder location are minor for this low-complexity operation.

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%, so the schema already documents activity_id and the fit/csv format enum. The description reinforces that fit is the downloaded Rouvy Activity file and csv is per-second records, but adds little beyond the schema's own parameter descriptions.

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 states a specific verb and resource: saving one Activity to the rider's export folder. It also identifies the two supported formats and their meanings, so an agent can distinguish this export operation from sibling read/list tools without opening the schema.

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 implies when this tool applies by saying it saves one Activity to the export folder, but it does not explicitly compare it with alternatives such as get_activity or get_activity_streams. It also does not state when not to use it or any prerequisite workflow for obtaining activity_id.

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