GitMCP

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Add files') but doesn't mention critical behaviors like whether this is a read-only or mutating operation (it's mutating), what happens on success/failure, or if there are side effects (e.g., staging files for commit). This leaves significant gaps for an agent to understand the tool's impact.

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 a single, efficient sentence with zero waste—'Add files to Git staging area' is front-loaded and directly conveys the core action. Every word earns its place, making it highly concise and well-structured for quick comprehension.

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 (a mutating operation with no annotations and no output schema), the description is incomplete. It doesn't explain the return values, error conditions, or behavioral nuances (e.g., how patterns work, what 'staging area' entails). For a tool that modifies state, this lack of context could lead to misuse by an agent.

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%, with both parameters ('path' and 'patterns') well-documented in the schema. The description adds no additional semantic context about parameters beyond implying files are involved, so it meets the baseline of 3 where the schema does the heavy lifting without compensating for gaps.

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 'Add files to Git staging area' clearly states the verb ('Add') and resource ('files to Git staging area'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like git_commit or git_status, which also interact with the staging area in different ways.

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 no guidance on when to use this tool versus alternatives like git_commit (which commits staged files) or git_status (which shows staging status). It lacks context about prerequisites (e.g., needing a git repository initialized) or exclusions, leaving the agent to infer usage from the tool name alone.

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