git-mcp-server

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

Annotations declare readOnlyHint=true. Description adds behavioral context by specifying exactly what 'status' encompasses (staged/unstaged/untracked), but omits edge cases or performance notes.

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?

Single, dense sentence (11 words) front-loaded with the core action. No redundancy or filler; every word specifies scope or content.

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?

Sufficient for a read-only status tool. Output schema exists to detail return structure, while description adequately covers conceptual content (the three file categories).

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% with clear descriptions for 'path' and 'includeUntracked'. Tool description adds no parameter-specific guidance, but the comprehensive schema makes this acceptable (baseline 3).

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?

Specific verb ('Show') and resource ('working tree status') with precise scope ('staged, unstaged, and untracked files'). Clearly distinguishes from siblings like git_diff (line changes) and git_log (commit history).

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 context about what the tool returns (three file categories), implicitly guiding when to use it. Lacks explicit comparison to alternatives (e.g., 'use this instead of git_diff when checking file states').

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