gitFetch

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

The description adds value beyond the readOnlyHint annotation by explaining that the tool updates remote-tracking branches without merging. This behavioral detail helps the agent understand the tool's effects. The description does not contradict the annotation; readOnlyHint is typically interpreted as a safety indicator rather than a strict literal read-only operation, and updating remote references is considered non-destructive.

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 concise—two sentences that front-load the core purpose and then provide context and an alternative. Every sentence adds value; there is no fluff. This is an excellent example of efficient communication.

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 simplicity (2 optional parameters, no output schema), the description covers the essential points: what it does, its effect on remote-tracking branches, and when to use an alternative. It does not describe the return value or potential errors, but for a fetch operation this is acceptable. The description is nearly complete for this tool.

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 the baseline is 3. The description does not add any additional meaning for the parameters beyond what the schema already provides. Both parameters ('remote' and 'all') are described in the schema, and the description mentions no extra details about their usage or defaults.

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 purpose: 'Fetch updates from a remote without merging.' It also distinguishes itself from gitPull by noting that gitFetch does not merge, and explains that it updates remote-tracking branches so that gitListBranches and gitCheckout see the latest state. This effectively identifies the tool's verb and resource 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 explicitly mentions the alternative 'Use gitPull to fetch and merge in one step,' providing clear guidance on when to use gitPull instead. However, it does not elaborate on specific scenarios for using gitFetch versus gitPull, such as preferring gitFetch when one wants to review changes before merging. This slight gap prevents a perfect score.

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