gitPull

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

Annotations declare destructiveHint: true, and the description adds that rebase provides linear history, which implies potential rewriting. However, it does not elaborate on risks like merge conflicts or loss of local commits. With annotations covering destructiveness, the additional context is moderate.

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?

Two concise sentences with front-loaded purpose. No redundant or extraneous information; every sentence adds value.

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 description lacks details on what the tool returns after a pull (e.g., merge status, conflict information) and does not mention potential side effects beyond the destructive hint. Given no output schema, it could provide more context on outcomes.

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?

Input schema covers all 3 parameters with descriptions (100% coverage). The description adds context by stating defaults ('Defaults to origin with merge'), which enhances understanding of parameter behavior beyond the schema alone.

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 'Pull changes from a remote into the current branch,' specifying the verb and resources. It distinguishes from siblings like gitFetch and gitPush by indicating merge vs rebase, and provides defaults (origin with merge), making the purpose unambiguous.

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 gives explicit guidance: 'Defaults to origin with merge. Use rebase: true for linear history.' It tells when to use the default and when to use rebase, but does not explicitly exclude alternative tools like gitFetch or explain when to avoid pulling entirely.

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