GitMCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'merge' implies a write operation, the description doesn't disclose critical behavioral traits: whether this creates a merge commit, what happens with conflicts, whether it requires a clean working directory, or what the expected output looks like. For a mutation tool with zero annotation coverage, this is inadequate.

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 extremely concise - a single sentence that directly states the tool's purpose. There's zero wasted language, and the information is front-loaded. This is an example of efficient communication.

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 git merge operation with no annotations and no output schema, the description is incomplete. It doesn't explain the behavioral implications of merging, potential side effects, error conditions, or what constitutes success. Given the complexity of git operations and the lack of structured safety information, this description leaves too many questions unanswered.

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 both parameters are documented in the schema. The description doesn't add any parameter semantics beyond what the schema already provides (repository path and source branch). It doesn't explain what 'current branch' means or how it's determined. Baseline 3 is appropriate when the schema does 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 ('a branch into current branch'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from potential alternatives like 'git_rebase' or explain how it differs from sibling tools like 'git_pull' that also involve merging.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like being in a git repository), when merging is appropriate versus rebasing, or what happens if there are conflicts. With multiple git-related sibling tools available, this lack of differentiation is a significant gap.

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