git_command

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

Despite no annotations, the description discloses blocked commands, mutation potential, timeout, and return values. It lacks detail on whether the tool changes working directory or has side effects beyond the repo, but overall provides strong behavioral 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 concise (5 sentences) and front-loaded with purpose. Every sentence adds value (path constraint, command parsing, blocked commands, timeout, return). No unnecessary words.

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 2 params, no annotations, and the presence of an output schema, the description sufficiently covers constraints, blocked operations, and return values. It is complete for the tool's complexity.

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?

With 0% schema coverage, the description compensates by explaining path constraints (allowed_write_dirs, .git) and command structure (after git -C <path>, shell-like quoting, no expansion). It adds meaning beyond the schema, though an example would improve clarity.

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 clearly states it executes a Git subcommand in an allowed local repository, distinguishing it from siblings like execute_shell_command. The verb 'uitvoeren' (execute) and resource 'Git-subcommando' are specific and unambiguous.

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 specifies when to use (Git operations in allowed repos) and provides explicit constraints: path must be under allowed_write_dirs and contain .git, blocked commands are listed, and quoting behavior is described. It could be improved by explicitly contrasting with execute_shell_command for non-Git tasks.

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