lerobot_build_command

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

No annotations are provided, so the description must fully disclose behavior. It states it's a dry-run, but does not explain what the preview output contains (e.g., the command string, parsed arguments, etc.), leaving the agent uncertain about the return value. The output schema exists but is not detailed in the description.

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 sentence, concise and to the point. It is appropriately front-loaded with purpose. However, it might be too brief, sacrificing clarity on details.

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 the presence of an output schema, the description does not need to detail return values, but it lacks context about what 'known LeRobot entry point command' means and how parameters like options or extra_args are used. Sibling tools are numerous, but no guidance on when to choose this over others is provided. Overall, the description is minimal and insufficient for a 5-parameter tool.

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 does not explain any of the 5 parameters (command, options, extra_args, cwd, use_uv). While parameter names give some hints, the description adds no value for understanding their meaning or usage.

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 uses the specific verb 'Preview' and clarifies 'without running it', clearly indicating a dry-run. This distinguishes it from sibling tools like lerobot_run_command, which actually executes the command.

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 to use the tool (for previewing before execution), but does not explicitly mention when not to use it or specify alternatives beyond the implied contrast with run commands. Still, the context is clear enough for an AI agent.

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