Git MCP

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. It does well by stating the read-only constraint and security rationale, and mentions support for both local and remote repositories. However, it lacks details on error handling, rate limits for remote operations, authentication needs, or what 'backup' specifically entails (e.g., creates archive files). For a tool with 14 parameters and no annotations, more behavioral context would be helpful.

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 efficiently structured in two sentences: the first states the core purpose and scope, the second adds important constraints. Every word earns its place, with no redundancy or fluff. It's front-loaded with the key information (read-only file management) and appropriately sized for the tool's complexity.

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 tool's moderate complexity (14 parameters, no output schema, no annotations), the description is adequate but has gaps. It covers the purpose, scope, and constraints well, but doesn't explain return values or error behaviors. For a tool supporting multiple operations (read, search, list, backup) with remote capabilities, more context about output formats or operation-specific behaviors would improve completeness.

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 already documents all 14 parameters thoroughly. The description adds value by grouping operations (read, search, list, backup) and clarifying the read-only nature, but doesn't provide additional parameter semantics beyond what's in the schema descriptions. This meets the baseline of 3 when schema coverage is high.

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's purpose as 'Read-only file management tool for repository files' with specific verbs (reading, searching, listing, backup) and resource (repository files). It explicitly distinguishes itself from siblings by emphasizing 'file content modification operations are not allowed,' which differentiates it from potential write-focused tools like git-update or git-reset.

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 clear context for when to use this tool: for read-only file operations on both local and remote repositories. It explicitly states 'File content modification operations are not allowed,' which helps exclude write use cases. However, it doesn't name specific alternative tools (e.g., when to use git-archive vs. backup here) or provide explicit exclusions beyond the general modification restriction.

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