git_pull

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds real context beyond them: it authenticates via VBSTUDIO_GIT_USERNAME/TOKEN and will not block on a hidden credential prompt. It does not say how merge conflicts or failures are surfaced, which keeps it short of a 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?

Two tight sentences, with the core action front-loaded and the authentication caveat immediately after. No filler, though the phrase 'never hangs on a hidden prompt' is slightly awkward.

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 no-parameter-required, no-output-schema mutation tool, the description covers auth and non-blocking behavior but omits what happens on conflict, whether it merges or rebases, and the meaning of the branch/remote arguments. Adequate but with clear gaps.

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 only 33% - just 'repo' is documented - and 'branch' and 'remote' are explained nowhere, neither in the schema nor in the description. With low coverage the description is expected to compensate, and it adds nothing about the parameters.

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?

States a specific verb and resource ('Pull from the repo's remote'), which cleanly separates it from git_push, git_clone, and git_status. It does not explicitly name a sibling or scope, but the operation is 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?

There is no guidance on when to use this versus git_clone (initial checkout) or git_push, and no mention of prerequisites such as being on a branch or having a clean tree. The agent is left to infer the context entirely.

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