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 mentions local vs. remote operations and provider requirements, which adds some context. However, it doesn't describe critical behaviors like what 'delete' does (permanent? reversible?), what 'publish' entails (to a registry?), error handling, or output format. For a tool with multiple operations including destructive ones, this is a significant gap.

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 two sentences that efficiently state the tool's purpose and key operational distinction (local vs. remote). It's front-loaded with the main idea and avoids unnecessary details. However, it could be slightly more structured by explicitly grouping operations or mentioning the tool's scope more clearly.

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 complexity (19 parameters, multiple operations including destructive ones like delete), no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, how operations behave, or critical constraints (e.g., authentication for remote ops). For a multi-operation tool with high parameter count, this leaves too many gaps for effective 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 already documents all 19 parameters thoroughly with descriptions and usage contexts (e.g., 'for download'). The description adds no additional parameter semantics beyond what's in the schema, such as explaining relationships between parameters or clarifying ambiguities. Baseline 3 is appropriate when the schema does all the work.

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 states this is a 'Git package management tool for package operations' and lists the supported operations (list, get, create, etc.), which provides a general purpose. However, it doesn't specify what kind of packages (e.g., npm, Maven) or clearly distinguish it from sibling tools like git-release or git-tags that might also handle packages. The purpose is understandable but somewhat vague about scope.

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 mentions that 'local operations work with package files, remote operations require a provider,' which gives some context about when provider is needed. However, it doesn't provide explicit guidance on when to use this tool versus alternatives (e.g., git-release for releases, git-tags for tags), nor does it specify prerequisites or exclusions. Usage is implied rather than clearly defined.

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