git-mcp-server

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

The description confirms the write-operation nature (consistent with readOnlyHint:false) by mentioning 'integrates changes,' but fails to disclose critical behavioral traits like potential for merge conflicts, creation of merge commits, or network requirements. With minimal annotations, more safety context was needed.

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. The first establishes the high-level operation; the second clarifies the mechanism (fetch+integrate) that distinguishes this tool from siblings. 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 and comprehensive parameter documentation, the description doesn't need to explain return values. However, for a state-modifying operation with complex branching behavior (merge vs rebase), it should mention conflict handling or failure modes to be fully complete.

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 schema adequately documents all parameters including rebase and fastForwardOnly behaviors. The description adds minimal parameter-specific semantics beyond implying the 'current branch' default, meriting the baseline score for high-coverage schemas.

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 uses specific verbs ('Pull', 'Fetches', 'integrates') with clear resources ('remote repository', 'current branch'). It effectively distinguishes from siblings by emphasizing the dual fetch-and-integrate nature, unlike git_fetch (fetch only) or git_merge (local integration only).

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 the workflow by stating it both fetches and integrates, it lacks explicit guidance on when to use git_pull versus running git_fetch followed by git_merge, or warnings about prerequisites like a clean working tree. No alternatives are named.

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