git-mcp-server

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

Adds valuable behavioral context beyond readOnlyHint=true annotation: specifies it provides 'structured review instructions' and an 'analysis framework' (suggesting formatted output, not raw git log), and clarifies data scope (commits for cross-referencing). Consistent with read-only safety profile.

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?

Three tightly constructed sentences with zero waste. Front-loaded with core purpose, followed by critical usage constraint (changelog file separation), and ending with parameter guidance. Every sentence earns its place.

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?

Complete conceptual coverage given rich input schema (100% coverage), presence of output schema, and annotations. Description successfully establishes the tool's role in the broader changelog analysis workflow without needing to duplicate output schema details.

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 coverage is 100%, providing complete parameter documentation. Description minimally references reviewTypes ('Pass one or more review types') but adds no semantic depth beyond schema definitions. Baseline 3 appropriate for high-coverage schemas.

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?

States specific action ('Gather git history context') and resource ('commits, tags') with clear purpose ('support LLM-driven changelog analysis'). Distinguishes from generic git_log by specifying changelog analysis context and from file tools by noting changelog files are handled separately.

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?

Provides clear when-not guidance ('Changelog file should be read separately') establishing separation of concerns. Lacks explicit comparison to git_log for when to use this versus standard log retrieval, but offers clear contextual guidance on tool boundaries.

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