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

No annotations are provided, so the description carries the full burden; it does disclose genuinely useful behavior (FIT output as base64, ZWO checked for well-formedness only rather than XSD, only structured workouts accepted). Against that it references a nonexistent output_file parameter and an undocumented "remote endpoint" mode, leaving the execution model ambiguous.

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 tight sentences with the core capability front-loaded and caveats trailing, no filler. One sentence spends its budget on a parameter that does not exist in the schema, which is waste rather than verbosity.

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?

With no output schema and no annotations, the description must define the return contract, and it does so only partially: FIT is base64, but the return shape for TCX/ZWO/GCN/KRD output is unspecified. The input-side story is also vague since no file-input parameter exists yet output_file is discussed.

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 input_format, output_format, ftp, and input_content semantics are already documented in structured fields, giving a baseline of 3. The description adds no new per-parameter meaning and its mention of output_file introduces a parameter the agent cannot actually supply.

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?

States a specific verb ("Convert") plus the resource (fitness data formats) and enumerates them, so the agent knows exactly what the tool does. It does not compare itself to siblings like kaiord_validate or kaiord_round_trip_validate, which is the only thing keeping it from a 5.

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?

Usage is implied by the format list, and the note that FIT output is base64 unless output_file is given hints at an output-mode choice. However, there is no explicit guidance on when to pick this over kaiord_validate or kaiord_round_trip_validate, and the referenced "output_file" does not exist in the schema, muddying the one piece of mode guidance offered.

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