git_add

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

With no annotations, the description does not disclose that git_add performs a write operation (staging files), nor does it mention any side effects or prerequisites. It only covers execution timing behavior, leaving core behavioral traits undocumented.

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 relatively short but includes a redundant 'Kali Agent MCP tool: git_add' prefix. It is front-loaded with timing advice rather than core purpose, but overall it is not overly 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?

Despite an output schema existing, the description omits the fundamental functionality and parameter meanings. With 8 parameters and no schema descriptions, the agent cannot determine how to use the tool effectively.

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?

The description explains the timing-related parameters (timeout_seconds, on_timeout, etc.) but fails to explain the essential Git parameters (path, paths, all_changes). With 0% schema description coverage, this is a significant omission.

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 does not explicitly state that this tool stages files for Git commit; it only mentions execution timing. The purpose is implied by the tool name but lacks clarity, and it does not differentiate from sibling git tools like git_commit or 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 on when to use git_add vs other git operations. The only usage advice given relates to timeout settings, not to choosing between this tool and alternatives.

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