git-mcp-server: Fetch remote

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

The description adds value beyond annotations by listing what the tool excludes and defaults, but does not fully disclose side effects beyond the schema. Given openWorldHint=true, more detail on potential side effects (e.g., updating remote tracking branches) would improve transparency. No contradiction with annotations found.

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 exceptionally concise, using three clear bullet-like lines. It front-loads the operation purpose and efficiently communicates defaults and exclusions without wasted words.

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 tool's complexity, the description covers the operation, return fields, defaults, and exclusions. The presence of an output schema reduces the need to describe return values. However, it could mention prerequisites (e.g., remote configured) and error conditions for fuller completeness.

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 covers all parameters (100% coverage), so the baseline is 3. The description provides general operation context but does not add specific parameter-level explanations beyond what the schema already offers.

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 'Fetch origin heads into the fixed origin-tracking namespace', specifying the verb, resource, and scope. It distinguishes from sibling tools like git_push and git_merge by focusing on fetching without merging or pushing, though it could be more explicit about when to use it over alternatives.

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 usage by providing defaults and exclusions, but it does not explicitly state when to use this tool versus siblings. It gives context (e.g., no tag updates, no custom refspec) that helps an agent understand constraints, but lacks clear when-to-use/when-not-to-use guidance.

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