git-mcp-server

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

The description aligns with readOnlyHint=true by emphasizing 'provides' and 'returns' rather than modifying state. It adds valuable context beyond annotations by distinguishing between custom configured workflows and default best practices, and noting that current repository status is included to guide actions.

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 three-sentence structure is efficient and front-loaded: sentence 1 states the core purpose, sentence 2 clarifies return value variations (custom vs default), and sentence 3 notes the inclusion of repository status. No redundant or wasted text.

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 existence of an output schema (which handles return value documentation) and 100% input schema coverage, the description provides adequate context. It appropriately covers the tool's retrieval nature, workflow customization aspects, and repository status integration without over-specifying.

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 parameter documentation is comprehensive in the schema itself. The description does not add parameter-specific semantics, but given the high schema coverage, the baseline score of 3 is appropriate.

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 provides/returns workflow steps and instructions for git wrap-up, distinguishing it from action-oriented siblings like git_commit or git_tag. However, it could more explicitly emphasize that this retrieves configuration rather than executes wrap-up actions.

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 implies usage context ('wrap-up workflow,' 'reviewing, documenting, and committing changes') but lacks explicit guidance on when to use this retrieval tool versus directly executing git commands. No alternative tools are mentioned.

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