git_fetch

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is largely supplied. The description adds one useful piece of context by signalling that pruning only happens when explicitly requested, but it never states what pruning deletes (remote-tracking branches) or that the operation contacts the network and may require credentials.

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 short sentence with no wasted words, and the core operation is front-loaded. The second clause is compressed to the point of being cryptic, but there is no padding or redundancy.

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 tool is simple (two optional parameters) and has an output schema, so return values need no explanation. Only the meaning of prune and the distinction from pull/merge operations are missing, which is a modest gap for a low-complexity 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 description coverage is 0%, so the description must carry the parameter burden. It does convey two key facts beyond the schema: the remote must already be configured (not a URL), and pruning is opt-in via an explicit flag; it says nothing about defaults, the origin fallback, or what pruning affects.

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 verb and resource are concrete ("Fetch one configured remote"), so the agent knows this is a git fetch limited to a single remote. However, it never distinguishes against pull (fetch + merge) or other siblings, and the trailing clause about pruning is ambiguous rather than clarifying scope.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. An agent must infer that this only updates remote-tracking refs and does not touch the working tree, and must infer when to prefer git_pull instead.

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