Stage files for commit in Git repositories. Use this tool to prepare changes for committing by specifying files or staging all modifications.
Stage files for commit
| Name | Required | Description | Default |
|---|---|---|---|
| files | No | Files to stage | |
| all | No | Stage all changes | |
| cwd | No | Repository path |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose any behavioral traits beyond the basic action. It fails to mention that staging is a preparatory step that does not commit changes or that it modifies the index, leaving the agent without critical context.
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 sentence with no wasted words, making it efficient. However, it might be too brief and could benefit from including key usage hints without becoming verbose.
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?
For a simple tool without an output schema, the description is minimally adequate. It covers the core purpose but lacks details on side effects, return values, or prerequisites, which would be helpful given the number of sibling tools.
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?
All three parameters are fully described in the input schema (100% coverage), so the baseline is 3. The description adds no additional meaning beyond what the schema provides.
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 'Stage files for commit' uses a specific verb 'stage' and clearly identifies the resource 'files for commit', distinguishing it from sibling tools like git_commit and git_status.
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?
No guidance is provided on when to use this tool versus alternatives, such as when to stage specific files using the 'files' parameter versus staging all changes with the 'all' parameter, or when to use git_add over git_commit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.