gitPullRepo

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

The description explicitly warns 'This WRITES every object the repository carries, overwriting what is there,' which is critical behavioral disclosure beyond the annotations. It also calls out the transport requirement. This gives an agent a clear picture of the side effects before invoking the tool.

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 two sentences with no filler. The core action is stated first, and the high-risk overwrite behavior is front-loaded. Every sentence earns its place.

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 write operation with no output schema, the description covers the main effect, the destructive overwrite behavior, and a key prerequisite. It could also explain what a successful pull returns or how branch selection interacts, but the essential invocation context is present.

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 adds meaningful parameter-level context by requiring a transport outside $TMP, clarifying an important constraint not expressed in the schema. It does not describe every parameter, but the schema already handles that.

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 a specific action ('Pull an abGit repository') and the target ('into its package'). It names the operation, the object, and the destination, and it can be distinguished from sibling tools like pushRepo, stageRepo, and checkRepo.

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 implies the use case: retrieve a repository's objects into the local package. It also adds the prerequisite that a transport outside $TMP is needed. However, it does not explicitly contrast this with alternatives such as checkRepo, stageRepo, or pushRepo, leaving context to be inferred.

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