efs_git

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

No annotations are provided, so the description must disclose behavioral traits. It lists mutating operations like add, commit, branch, and stash, but gives no warning about side effects, permission requirements, reversibility, or impact on the repository. This is a significant gap for a tool that can modify state.

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 extremely concise: two sentences with a clear front-loaded subject and an enumerated list of operations. Every word earns its place and there is no redundancy or filler.

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?

This tool supports eight different operations with multiple parameters and no output schema, yet the description provides only a high-level list. It lacks operation-specific detail, examples, output expectations, or guidance on parameter combinations, leaving a substantial usability gap for an agent trying to invoke it correctly.

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%, so the structured schema already documents all parameters. The description adds no new parameter-level meaning beyond the schema, except for emphasizing that repoPath is required, which is already in the schema as a required field.

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 explicitly lists the git operations (status, diff, log, blame, add, commit, branch, stash) and states the required resource (repoPath). This clearly distinguishes it from sibling efs_* tools that handle file operations rather than git commands.

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 implies use for git operations and notes that repoPath is required, which is helpful context. However, it does not explicitly state when to prefer this tool over alternatives or provide exclusions/when-not-to-use guidance.

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