lerobot_convert_dataset_to_latest_format

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 discloses default local behavior and the effect of `force_conversion`. However, it does not specify if the conversion modifies the original data, creates a new version, or any potential side effects like overwriting files. More detail on the conversion process would improve transparency.

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 concise with two short paragraphs. The first paragraph states the core purpose, and the second adds key details. It is front-loaded and avoids unnecessary fluff, though it could be more structured with clear sections.

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 11 parameters, zero schema descriptions, and no annotations, the description is incomplete. It explains the main conversion and a key parameter but leaves most parameters (root, branch, file sizes, push_to_hub, etc.) unexplained. The output schema exists but the description does not mention return values or side effects.

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. It explains `repo_id` implicitly and `force_conversion` explicitly. However, 9 out of 11 parameters (e.g., root, branch, data_file_size_in_mb, push_to_hub, timeout_seconds, use_uv, env) are not described at all. The description adds minimal meaning beyond the schema.

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 the tool's purpose: 'Convert a LeRobot v2.1 dataset to the current v3.0 parquet layout.' It specifies the source format (v2.1) and target format (v3.0), distinguishing it from sibling tools that handle other conversion types or builds.

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 context on when to use: defaults to local/no-push behavior, and explains the `force_conversion` parameter for overriding existing v3.0 tags. It also notes that older versions must first be migrated to v2.1. However, it doesn't explicitly compare with sibling tools like `lerobot_forge_convert` or state when not to use this tool.

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