git

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

With no annotations, the description carries the full burden, yet it discloses almost nothing beyond 'local' and the vague qualifier 'allowed'. It never states that an allowlist governs which subcommands will succeed, nor that remote operations fail, nor how results are returned.

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?

It is a single front-loaded sentence with no filler, which is structurally fine. But the brevity comes at the cost of substance — it is under-specified rather than efficiently concise for a 4-parameter CLI wrapper.

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 tool with 4 parameters, a nested env object, no annotations, and no output schema, the description is far too thin. It omits the allowlist behavior, sibling routing, and any notion of what the call returns, leaving the agent to infer nearly everything.

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 schema already documents cwd, env, args, and the command allowlist caveat; baseline 3 applies. The description adds no additional parameter meaning beyond what the schema states.

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?

States a concrete verb and resource ('Run ... git subcommand') scoped to local execution, which is clear enough to understand the tool. However, it gives no differentiation from the 26 sibling wrappers (git_status, git_commit, etc.), so an agent cannot tell from the description alone when this generic entry point is the right choice.

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?

There is no guidance on when to use this generic tool versus the dedicated per-subcommand siblings, which is the single most important routing decision here. The only restriction hint ('allowed') lives in the word choice and is expanded only in the schema, not in the description.

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