git-mcp-server

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

Annotations indicate readOnlyHint: false, and the description aligns by mentioning mutation operations (add, remove, rename, set-url). However, it adds no further behavioral context such as what files are modified (.git/config), whether operations are reversible, or error conditions. Adequate given the annotation coverage but minimal added value.

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?

Single, efficiently structured sentence that front-loads the verb and resource. Every clause corresponds to a core capability with zero redundancy or filler. Excellent information density.

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 100% schema coverage, existence of output schema, and clear annotation indicating mutability, the description provides sufficient context for an agent to invoke the tool. Minor gap: does not clarify conditionally required parameters (e.g., 'name' is required for add/remove but not list), though the schema enumerates these fields.

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%, establishing a baseline of 3. The description reinforces the 'mode' parameter by listing the enum values in prose, but does not add semantic depth regarding parameter relationships (e.g., that 'add' requires both 'name' and 'url') beyond what the schema 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?

Lists specific operations (list, add, remove, rename, get/set URLs) and identifies the resource (remote repositories). Distinguishes from siblings like git_clone or git_fetch by focusing on configuration management rather than data transfer or initialization, though it doesn't explicitly contrast with these alternatives.

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?

Enumerates possible operations but provides no explicit guidance on when to use this tool versus siblings (e.g., when to use git_remote add vs git_clone). Usage is implied by the operation list, but there are no exclusions, prerequisites, or conditional logic explained.

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