update_git_repo

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

With no annotations, the description must disclose side effects, but it only says 'Pull/update'. It does not mention whether local changes might be overwritten, if the working tree must be clean, or what happens with branches. The mutating behavior is implied but not detailed.

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 a brief, front-loaded phrase that gets to the point. It is not cluttered, though it could arguably include more detail without hurting conciseness.

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 with only two parameters and no output schema. The description gives the basic operation but lacks context about return values, failure modes, or interaction with the remote. It is adequate but not thorough.

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 100% for both parameters, so the baseline is 3. The description itself adds no additional meaning beyond the schema's 'Branch to update' and 'Repository path', but the schema is already sufficient.

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 verbs 'Pull/update' with the resource 'Git repository', making the core action clear. It distinguishes itself somewhat from sibling tools like deploy_git_repo by implying a fetch/merge rather than a deployment, though it does not explicitly call out this distinction.

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?

No guidance is provided on when to use this tool versus alternatives such as deploy_git_repo or create_git_repo. There are no prerequisites, branch handling rules, or context about typical workflows.

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