Code MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Pull changes from remote' implies a network operation that updates the local repository, but it doesn't describe what happens on failure (e.g., merge conflicts), whether it requires authentication, if it's destructive (it can overwrite local changes), or the output format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 extremely concise ('Pull changes from remote')—a single phrase that front-loads the core action. There is zero wasted text, and every word earns its place by directly conveying the tool's purpose without redundancy or fluff.

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?

Given the complexity (a Git operation with potential side effects), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like error handling, prerequisites, or what the tool returns (e.g., success/failure status, merge output). For a tool that modifies local state and interacts with remotes, more context is needed to use it effectively.

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 input schema has 100% description coverage, with clear parameter descriptions: 'remote' (remote name), 'branch' (branch name), and 'cwd' (repository path). The description adds no additional meaning beyond the schema, such as default values (e.g., 'origin' for remote, current branch for branch) or usage examples. With high schema coverage, the baseline score of 3 is appropriate.

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 'Pull changes from remote' clearly states the verb ('Pull') and resource ('changes from remote'), making the purpose immediately understandable. It distinguishes from siblings like git_push (which pushes changes) and git_status (which shows status). However, it doesn't specify that this is a Git operation (though the tool name implies it) or mention the local repository aspect.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., having a Git repository initialized, being in a Git directory), when not to use it (e.g., during merge conflicts), or alternatives like git_fetch for fetching without merging. Usage is implied from the name but not explicitly stated.

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