git-sync

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

No annotations exist, so the description bears the full burden. It states the basic operations but omits critical details: whether it forces push, handles merge conflicts, requires authentication, or the behavior on failure. This lack of transparency could lead to unintended data loss.

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—one sentence of 8 words. It is front-loaded and to the point, but slightly too terse; a tad more context would improve clarity without sacrificing brevity.

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 (two git operations) and lack of output schema or annotations, the description omits important outcomes: what happens on success (e.g., output format), error states (e.g., merge conflicts, network issues), and usage context (e.g., must have commits staged). This is insufficient for a reliable agent invocation.

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?

With 100% schema description coverage for the single parameter 'directory', the baseline is 3. The description adds no extra meaning beyond the schema; it does not explain the parameter's role in the synchronization process.

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 'Synchronize repository: pull from remote, then push local changes', specifying the verb 'synchronize' and the resource 'repository' with explicit steps. This distinguishes it from sibling tools like git-pull and git-push, which perform only one direction.

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. For example, it does not mention that for a simple fetch or push, other sibling tools are more appropriate, nor does it indicate prerequisites (like needing to stage and commit changes first).

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