Code Buddy

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies execution of commands but doesn't disclose critical traits like permissions needed, side effects (e.g., file modifications), error handling, or output format. This is inadequate for a tool that can perform diverse operations.

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 with a single sentence, which is efficient. However, it's under-specified rather than appropriately sized—it lacks necessary details for a tool with broad capabilities, slightly reducing its effectiveness.

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 the complexity of Git operations, lack of annotations, and no output schema, the description is incomplete. It doesn't cover usage scenarios, safety considerations, or expected results, making it insufficient for an agent to reliably invoke this tool across varied contexts.

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 fully documents the two parameters (command and cwd). The description adds no meaning beyond this, such as examples of valid commands or cwd usage, resulting in a baseline score of 3.

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 'Run git commands' states the general purpose (execute Git operations) but is vague about scope and resources. It doesn't specify what types of Git commands are supported or distinguish this from sibling tools like git_diff, git_log, and git_status, which handle specific Git operations.

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. It doesn't mention when to prefer this general-purpose Git tool over the specific sibling tools (git_diff, git_log, git_status) or other command-execution tools like run_command, leaving the agent without context for selection.

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