git_init

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

Beyond annotations (which only indicate non-read-only, non-idempotent, non-destructive), the description discloses meaningful behavioral traits: it creates missing directories, refuses non-empty directories, validates the target, and returns a confirmation text. This is valuable context an agent needs to anticipate side effects and failure modes.

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 five sentences long, every sentence contributes either purpose, usage guidance, exclusions, or behavioral detail. It is front-loaded with the core action and remains compact without unnecessary 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?

The tool is simple with a small parameter set. The description covers purpose, when-to-use, what it does, what it refuses, and the shape of the return value. With no output schema, this is sufficient contextual coverage.

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 input schema already documents all three parameters at 100% coverage, so baseline is 3. The description adds extra context by mentioning 'non-standard initial branch or bare layout' and instructing the agent to 'pass an empty or missing target,' which helps map usage scenarios to parameters.

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 opens with an explicit verb-phrase: 'Initialize a new git repository in repo_path, creating the directory if missing.' It clearly identifies the resource (a new git repo) and distinguishes itself from git_clone by explicitly stating it does NOT clone existing projects.

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 provides explicit when-to-use guidance ('Use this when starting a brand-new project...'), an explicit exclusion ('Does NOT clone existing projects — use git_clone'), and a 'Best for' recommendation. This gives the agent clear decision criteria among siblings.

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