lerobot_build_forge_convert

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

No annotations provided; description says 'preview' but doesn't clarify if actual conversion occurs or if it's a dry run. No mention of destructive potential, auth needs, or side effects.

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?

Single sentence is concise but lacks detail. Could be improved by adding key parameter context; not overly verbose.

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 12 parameters and no annotations, the description fails to provide enough context. No information on return values, required parameters beyond names, or how to use optional parameters.

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%, and the description adds no meaning to the 12 parameters. Terms like 'source', 'output', 'target_format' are not explained; user must infer from names.

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?

Description clearly states the tool converts Forge datasets to/from LeRobot formats. 'Preview' and 'pinned' add specificity but could be clearer; overall it distinguishes from sibling 'lerobot_forge_convert' which likely does the actual conversion.

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 guidance on when to use this tool vs alternatives like 'lerobot_forge_convert' or 'lerobot_convert_dataset_to_latest_format'. Does not specify prerequisites or when to use dry_run.

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