git_clone

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

With no annotations, the description carries the full burden. It discloses the core behavior (cloning into VBS_WORKSPACE_DIR) and the side effect (discoverability by list_repos), but it does not address potential overwriting, failure modes, authentication requirements, or what happens if destName 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?

The description is two concise sentences with no filler. It front-loads the action and destination, then adds the purpose and usage context, making every word deliver value.

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 simplicity of a clone operation with two well-documented parameters and no output schema, the description adequately covers the purpose, destination, and integration with list_repos. It could mention error handling or prerequisites (e.g., network, credentials), but the essential context is present.

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 for both parameters, so the baseline is 3. The description does not add any parameter-specific detail beyond what the schema already provides, only reaffirming the destination directory.

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 ('Clone a git remote'), the target resource (git remote), and the destination (VBS_WORKSPACE_DIR), while also distinguishing it from siblings like git_pull and list_repos by noting its role in making repos discoverable via list_repos.

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 clear context for when this tool is used (to clone a remote into the workspace for discovery by list_repos, specifically in /link's VBS setup flow), but it does not explicitly mention when not to use it or name alternative tools for related operations like updating an existing repo.

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