git-mcp-server

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

Annotations declare readOnlyHint=false (mutative), and the description adds that commits are 'reapplied' and history becomes 'cleaner,' which hints at rewriting. However, it omits key behavioral traits: that commit hashes change, that conflicts may require manual resolution, or that this is a destructive history rewrite.

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 efficiently structured: first defines the action, second explains the mechanism and value proposition. No redundant or wasted words.

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 100% schema coverage and existence of an output schema, the description adequately covers the basics. However, for a complex stateful git operation with conflict potential, the description is minimal—it fails to prepare the agent for the multi-step process or explain what happens in the output schema (likely rebase progress/conflict status).

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 baseline is 3. The description mentions 'onto another branch' which loosely references the upstream/onto parameters, but adds no syntax clarification, examples, or explanations of the stateful mode workflow (start/continue/abort/skip) beyond what the schema enum already 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?

The description clearly states the tool reapplies commits onto another base for a cleaner history, using specific verbs (rebase, reapplies). The 'cleaner history' phrase implicitly distinguishes it from git_merge (which creates merge commits), though it could explicitly mention the linear history advantage.

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 choose rebase over merge (sibling tool), nor warnings about rebasing public/shared branches. The description lacks prerequisites (e.g., clean working directory) and doesn't explain the multi-step workflow implied by the mode parameter (start/continue/abort).

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