rp_fetch_repo

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

With no annotations, the description carries the full burden and does well: it discloses idempotency, that force=true deletes and redownloads, that no git binary or Vivado session is needed, and that it returns repo_path. It does not mention network/auth requirements or what happens on download failure, so it is not fully complete.

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?

Three tight sentences with the action and its constraints front-loaded, followed by the return-value handoff and the idempotency caveat. No filler.

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 zero-required-parameter fetch tool with no output schema, the description covers what the agent needs: what it does, that it needs no git or Vivado session, what it returns (repo_path), and how to force a refresh. The remaining details (timeout, URL override) are fully covered by the schema.

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 100%, so the schema already documents ref, url, force, timeout, and dest_path thoroughly. The description only restates the force/redownload behavior and the ref-to-directory naming, adding little beyond the structured fields.

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 states a specific verb and resource — download the RedPitaya-FPGA repo from GitHub as a zip and extract it — plus the key implementation constraint (no git, stdlib only). It clearly distinguishes this from the sibling rp_setup_workspace, which consumes the resulting repo_path.

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?

It routes the agent explicitly: the returned repo_path feeds into rp_setup_workspace, and it notes no Vivado session is required, which is meaningful in a toolset dominated by Vivado session tools. It lacks an explicit 'when not to use' (for example, when the repo already exists locally), so it stops short of a 5.

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