git-mcp-server

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

The annotation provides readOnlyHint: false, confirming this is a write operation. The description adds valuable context about protocol support and shallow cloning, but fails to disclose critical behavioral traits like error handling when localPath already exists, directory creation behavior, or authentication mechanisms for private repos.

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 consists of exactly two efficient sentences with zero redundancy. The first sentence establishes the core operation, and the second adds capability details (protocols/shallow cloning). Every word earns its place.

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 existence of an output schema, return values need not be described. However, for a filesystem-mutating operation with 6 parameters, the description lacks operational details such as conflict resolution behavior, disk space requirements, or network dependency warnings that would help an agent handle failures gracefully.

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?

With 100% schema description coverage, the baseline is appropriately met. The description references 'shallow cloning' (mapping to the depth parameter) and protocol support (mapping to URL format), but adds minimal semantic meaning beyond what the well-documented schema already provides.

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 specific action (clone), resource (repository), and scope (remote URL to local path). It effectively distinguishes from siblings like git_init (which creates empty repositories) and git_pull (which updates existing ones) by emphasizing the remote-to-local copy operation.

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?

While the description implies usage by mentioning HTTP/HTTPS/SSH support and shallow cloning, it lacks explicit guidance on when to use this versus alternatives (e.g., 'use git_init for creating new empty repositories instead') or prerequisites (e.g., authentication requirements for private repositories).

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