litex_build

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool 'Returns logs and output directory', which gives some insight into outputs, but fails to describe critical behaviors like whether this is a read-only or destructive operation (e.g., does it modify files or create new ones?), potential side effects, error handling, or execution environment requirements. For a build tool with zero annotation coverage, this is a significant gap in 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 extremely concise—just one sentence that efficiently conveys the core action and outputs. It is front-loaded with the main purpose ('Run LiteX board target with --build') and avoids any unnecessary details, making it easy to parse quickly. Every word earns its place, with no wasted verbiage.

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 complexity of a build tool (which typically involves compilation, file generation, and potential side effects), no annotations, and no output schema, the description is incomplete. It lacks information on what the build does (e.g., generates hardware binaries, software images), how outputs are structured, error conditions, or dependencies. The mention of 'Returns logs and output directory' is helpful but insufficient for a tool that likely has significant behavioral nuances.

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?

The input schema has 100% description coverage, providing clear documentation for all four parameters (board, args, output_dir, timeout). The description adds no additional parameter semantics beyond what the schema already states, such as explaining the format of 'board' values or typical use cases for 'args'. Given the high schema coverage, a baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 action ('Run LiteX board target with --build') and the resource ('LiteX board target'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from its sibling 'litex_flow' or 'litex_soc', which appear related to LiteX workflows, leaving some ambiguity about when to choose this specific build tool over others.

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 no guidance on when to use this tool versus alternatives like 'litex_flow' or 'litex_soc'. It mentions the '--build' flag but doesn't explain the context or prerequisites for running a build, such as needing a configured project or specific input files. This lack of comparative or contextual guidance limits its usefulness for tool selection.

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