Git MCP

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions the four operation types but doesn't disclose critical behaviors like whether operations are destructive, what permissions are required, how errors are handled, or what output formats to expect. For a tool with 12 parameters and multiple operations, this leaves significant gaps in understanding tool behavior.

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 exceptionally concise and well-structured in a single sentence that efficiently communicates the tool's scope and four main operations. Every word earns its place with zero redundancy or unnecessary elaboration, making it easy to parse quickly.

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 complex tool with 12 parameters, 4 distinct operations, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain how operations differ, what each returns, error conditions, or behavioral nuances. The agent would need to rely heavily on parameter names and schema descriptions to understand proper usage.

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%, providing comprehensive parameter documentation. The description adds minimal value beyond the schema, only implying that parameters relate to archive operations without explaining how they interact across different actions. The baseline score of 3 reflects adequate schema coverage despite the description's limited contribution.

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 performs 'archive operations for Git repositories' and enumerates the four specific operations (create, extract, list, verify). It distinguishes this from sibling tools like git-branches or git-tags by focusing on archive functionality, though it doesn't explicitly contrast with similar tools like git-backup.

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 when to choose git-archive over git-backup or other sibling tools, nor does it specify prerequisites or appropriate contexts for each operation type. The agent must infer usage from the operation names alone.

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