Git MCP Server

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose that this is a destructive/mutative operation, potential permission requirements, side effects (e.g., branch deletion if 'delete_branch' is true), or error conditions (e.g., merge conflicts). The description is minimal and misses critical context for safe invocation.

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 is a single, efficient sentence with zero waste. It's front-loaded with the core purpose and includes a brief clarification for GitLab users, making it appropriately sized and structured.

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?

For a destructive tool with 5 parameters, no annotations, and no output schema, the description is inadequate. It lacks behavioral transparency, usage guidelines, and details on return values or errors. Given the complexity and mutation nature, more context is needed to ensure safe and correct use.

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 fully documents all 5 parameters. The description adds no parameter-specific information beyond what's in the schema, such as explaining interactions between parameters (e.g., 'squash' and 'commit_message'). Baseline 3 is appropriate as the schema handles the heavy lifting.

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 action ('merge') and target resource ('pull request'), with a helpful parenthetical clarifying GitLab terminology. It distinguishes from siblings like 'create_pull_request' or 'get_pull_request' by focusing on the merge operation, though it doesn't explicitly contrast with all potential 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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., pull request must be mergeable), exclusions (e.g., conflicts), or related tools like 'create_pull_request' for creation or 'get_pull_request' for checking status.

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