git_pull

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

Annotations indicate readOnly=false and destructive=false. The description adds meaningful behavioral context: the pull performs a merge or rebase into the current branch, conflicts are surfaced as errors, and rebase=True changes the commit graph shape. It also clarifies it does not merely fetch. This goes beyond the annotations, though it could mention prerequisites like a clean working tree or authentication, hence a 4 rather than 5.

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 compact and front-loaded: it opens with the core action, quickly gives the primary use case, the main flag behavior, a sibling alternative, and the return format. Every sentence carries meaning without redundancy.

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 tool's moderate complexity, the description covers the main use case, the key parameter behavior (rebase), the conflict outcome, and even provides the return value format ('Pulled from 'origin'.' followed by per-ref lines'). It also names the alternative tool. This is sufficient for an agent to decide when to invoke git_pull and what to expect.

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 coverage is 100%, so each parameter is already described. The description adds a small nudge for rebase ('rebase=True to keep a linear history'), but overall it does not add significant meaning beyond the schema's parameter descriptions and defaults. A baseline of 3 is appropriate because the schema already does the heavy lifting.

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 the tool's primary action: 'Pull from a remote and merge (or rebase) into the current branch.' It uses specific verbs and resources, and explicitly distinguishes itself from git_fetch ('Does NOT fetch only — use git_fetch...'). This makes the purpose unambiguous and differentiates it from siblings.

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 usage guidance: 'Use this to sync local work with upstream changes,' and gives a conditional alternative via rebase=True for linear history. It also explicitly notes when NOT to use it (fetch-only use git_fetch) and how to handle conflicts ('conflicts are reported as errors, resolve and retry').

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