git_pull

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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the mutation and network profile is covered. The description adds real value by disclosing that local changes are NOT auto-stashed and that ff-only is the integration default, both of which affect whether the call succeeds. It still omits what happens on conflict, whether tracked files are overwritten, and how failure surfaces.

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 terse clauses, front-loaded with the operation and then the notable constraint. Nothing is wasted, though the telegraphic phrasing borders on underspecification rather than genuine concision.

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 explained. But for a destructive, network-facing mutation with three undocumented parameters at 0% schema coverage, the description leaves too much to inference — particularly the meaning of the branch/remote arguments and the consequences of the non-default strategies.

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 carries the full burden for branch, remote and strategy. It only confirms that strategy defaults to ff-only (already in the schema default) and says nothing about what branch or remote mean when omitted, nor what merge/rebase strategies imply.

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 says 'Pull' and names a concrete behavioral trait (no auto-stash) plus the default strategy, so the core operation is identifiable. However, it never explains what a pull does in this context (fetch+integrate) or how it differs from the nearby git_fetch, git_merge and git_rebase siblings, leaving distinction to the name alone.

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?

There is no statement of when to use git_pull versus git_fetch, git_merge or git_rebase, and no prerequisites such as clean working tree or configured upstream. The 'without auto-stash' clause hints at a constraint but is phrased as behavior, not as guidance.

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