git_init

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

The parenthetical 'non-destructive; existing repos are left intact' restates what destructiveHint=false already conveys, though it usefully clarifies the edge case of running against an existing repository. It says nothing about what is actually created (a .git directory at the given path) or that the branch is set at creation time.

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?

A single front-loaded sentence with zero filler; the resource and the safety caveat are both stated up front.

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?

An output schema exists, so return values need not be described, and the tool has no required parameters. The remaining gap is that neither input is explained anywhere, which matters for a tool whose two knobs (target path, initial branch name) determine the outcome.

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 0%, so the description must compensate for both parameters, and it does not mention 'repo' or 'initial_branch' at all. Their defaults ('.' and 'main') and meaning are left entirely to the schema's bare titles, which the description does nothing to clarify.

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 states a specific verb and resource ('Initialise a new git repository'), which is unambiguous. No sibling tool performs repository creation, so confusion risk is low, though it never explicitly differentiates itself from the surrounding git_* tools.

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?

Usage is only implied: an agent can infer this is the tool to bootstrap a repo. There is no statement of prerequisites (e.g., path must exist), when not to use it, or which sibling to prefer for an already-initialised repo.

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