lerobot_forge_convert

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

No annotations provided, so the description carries full burden. It mentions using 'Forge main at the pinned bug-fix commit,' which gives some deterministic behavior, but fails to disclose side effects (destructive or not), required permissions, error handling, or output behavior. Insufficient for a conversion tool.

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 very concise (two sentences), but it omits critical information that would fit within a few more sentences. It is not overly verbose, but the brevity comes at the cost of completeness.

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 tool with 15 parameters and an output schema, the description provides no context on return values, parameter usage, or workflow integration. It does not explain the conversion process, input formats, or output structure. Incomplete for practical use.

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% (no parameter descriptions in schema or description). The description adds no meaning to any of the 15 parameters. Baseline is 3 for high coverage, but here coverage is low and description fails to compensate, leaving parameters entirely undocumented.

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 that the tool runs a pinned Forge dataset conversion using a specific bug-fix commit. It distinguishes from siblings like 'lerobot_convert_dataset_to_latest_format' and 'lerobot_build_forge_convert' by emphasizing the pinned version, but the phrase 'pinned' is not elaborated.

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?

No explicit guidance on when to use this tool vs alternatives. The description does not mention prerequisites, context, or when not to use it. Sibling tools like 'lerobot_convert_dataset_to_latest_format' or 'lerobot_build_forge_convert' are not referenced or contrasted.

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