git-mcp-server

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

Annotations only declare readOnlyHint: false. The description adds that it 'Downloads objects and refs' (confirming local modification) and specifies the no-merge behavior. However, it omits details about updating remote-tracking branches, network requirements, or idempotency.

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 sentences with zero waste. Front-loaded with the core action ('Fetch updates'), followed immediately by the critical behavioral distinction ('without merging'). 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?

Appropriate for the complexity: 5 optional parameters with 100% schema coverage and an output schema available. The description captures the essential fetch semantics, though it could explicitly mention 'remote-tracking branches' for completeness given the 'refs' terminology may be opaque.

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 does not add parameter-specific semantics (e.g., when to use depth for shallow clones vs full fetch), but the schema adequately documents all 5 optional parameters without needing supplementation.

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?

Specific verb (Fetch) + resource (remote repository). The phrase 'without merging them' effectively distinguishes this from git_pull and git_merge siblings, clarifying that it only downloads without integrating changes into the working directory.

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?

Implicitly suggests usage via 'without merging them' (implying use git_pull instead if merging is desired), but lacks explicit guidance on when to choose this over alternatives or workflow recommendations (e.g., 'use before git_merge to inspect changes').

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