repository_fetch

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

With no annotations provided, the description carries the behavioral disclosure burden. It transparently states that the fetch is explicit and that the working tree will not be changed, a crucial safety-relevant trait. It does not cover authorization, network failure, or which local refs are updated, but it reveals the essential non-destructive-to-worktree behavior.

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, front-loaded sentence that states the operation, scope, and behavioral guarantee with no filler. It is as concise as possible while conveying the main distinction.

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 fetch operation with an output schema and standard Git parameters, the core usage is clear, but the lack of parameter explanations and explicit sibling routing leaves tangible gaps. It is adequate for a simple tool but not fully self-sufficient.

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?

The schema has four parameters at 0% description coverage, and the tool description names none of them. Terms like prune and include_tags are left entirely to the agent to infer, so the description does not compensate for the missing schema documentation.

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 uses the specific verb 'fetch' with the resource 'configured remote' and adds the key scoping constraint 'without changing the working tree.' This clearly distinguishes it from repository_pull and repository_clone. It is not a tautology and names a concrete operation.

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?

It communicates the primary use case—retrieving remote updates without touching the working tree—which implies it should be preferred over repository_pull when no merge or local file update is desired. However, it does not explicitly name sibling alternatives or state when not to use it, so some inference remains.

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