git-pull

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

Lacks disclosure of key behaviors: that git-pull performs a fetch followed by a merge (or rebase), may cause merge conflicts, and modifies the local branch. No annotations exist to compensate.

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 sentence is concise but omits important context that would help an agent decide correctly. It earns its place but could be more informative without extra length.

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?

For a simple tool with one optional param and no output schema, the description is minimally adequate. However, it fails to differentiate from similar tools among the many siblings.

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% with one optional parameter. The description does not add meaning beyond the schema, but high coverage makes a baseline 3 appropriate.

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 action ('pulls') and the resource ('changes from the remote repository'), making the purpose evident. It distinguishes from siblings like git-push or git-clone, though could be more specific about integrating changes into the current branch.

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 on when to use git-pull versus related tools like git-fetch, git-merge, or git-rebase. The description does not mention prerequisites, such as being on the target branch or having a clean working directory.

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