clone_reference_repo

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

No annotations are provided, so the description carries the full behavioral burden. It usefully characterizes the result as a 'read-only reference' and fixes the write location (third-party/), but says nothing about network requirements, clone duration/size, or what happens if the destination already exists.

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?

Two tightly written sentences, front-loaded with the action, destination, and accepted values, followed by the usage condition. Every clause carries information; 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?

An output schema exists, so return values need no explanation, and the description covers action, destination, repo values, and intent. It falls slightly short given zero annotation coverage and zero schema descriptions, leaving the workspace parameter and network/overwrite behavior unaddressed.

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 coverage is 0%, so the description must compensate. It adds real value for 'repo' by listing accepted values (none of which appear in the schema as an enum) and pins 'dest' to third-party/, but the required 'workspace' parameter is never explained.

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?

States a specific verb (Clone) plus resource (a reference implementation) and the exact destination (third-party/), and enumerates the accepted repo values (reactos, wine, qemu, virtio-win, or any git URL). No sibling tool performs a clone, so an agent can identify this unambiguously.

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?

Provides an explicit trigger condition: 'Clone repos as needed when a component needs proven patterns or test suites.' There is no overlapping alternative among the siblings, so no exclusions are needed, but it stops short of stating prerequisites (e.g., network availability).

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