Pull From Git

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

Annotations declare readOnlyHint=false, so the mutating nature is already known. The description adds no extra context beyond the fact that it pulls changes. It does not mention potential merge conflicts, stashing, or failure modes, but this is not a contradiction. A middle score is appropriate because the description adds minimal behavioral info beyond annotations.

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 single, direct sentence with no filler. It is front-loaded with the verb and clearly identifies the target. Perfectly concise for the tool's simplicity.

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 two parameters and no output schema. The description is adequate for a basic pull operation, but it omits any caveats like merge conflicts, local changes preservation, or what the return value represents. Since openWorldHint=true indicates external interaction, a bit more context would be helpful.

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% with descriptions for both agent_id and branch. The tool description adds nothing new about parameters, so the baseline of 3 is correct since the schema carries the semantic burden.

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 action ('Pull') and the resource ('the latest changes from git for an agent's repo'). It distinguishes from sibling git tools by identifying the exact operation (pull vs status, commits, branches, etc.).

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 given on when to use this tool vs alternatives. With many sibling git tools (merge, switch, list, etc.), the description does not explain scenarios (e.g., 'use to sync before editing') or call out alternatives/conflicts.

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