Clone

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=false, and destructiveHint=false, so the safety profile is covered structurally. The description adds only one behavioral fact — that arbitrary host commands are prohibited — without explaining what a clone overwrites, whether existing directories are replaced, or how the multi-action surface (status/cancel/phased_push) behaves.

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 short sentences are front-loaded and waste no words, which is structurally fine. However, the content is thin and the second clause describes the family rather than this tool, so brevity here reflects under-specification rather than disciplined economy.

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?

This is an 11-parameter, multi-action mega-tool with no required parameters and an output schema, and the description never explains its action model or how path, projects, command, and job_id interact. Even with the output schema handling return values, the description is far too sparse for the tool's complexity.

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 all 11 parameters including their action-scoped meanings. The description contributes no additional parameter guidance, which puts this at the baseline 3 for a fully documented schema.

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?

"Clone (rm_git)" essentially restates the name and title, and the second clause ("Typed bulk Git operations") describes a family of Git operations rather than this tool's specific job. The schema shows this tool spans actions like phased_push, status, cancel, commit, and raw, so the description does not distinguish it from siblings such as rm_git_push, rm_git_status, or rm_git_raw.

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?

There is no when-to-use or when-not-to-use guidance, and no routing to the many siblings that clearly overlap (rm_git_pull, rm_git_push, rm_git_phased_push, rm_git_status, repository_manager_clone_projects). The only rule given ("arbitrary host commands are prohibited") is a blanket restriction, not a selection criterion.

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