Pull remote changes

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

With no annotations provided, the description carries the full burden. It discloses side effects: performs a merge, downloads files, writes a sync stamp to '.mcs/cs-sync.json', and explains how that stamp interacts with cs_check_drift. It doesn't mention conflict handling or reversibility, but it is specific about observable state changes.

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 compact trio of sentences: purpose, usage timing, and side-effect/follow-up. It front-loads the core action and avoids fluff. It is slightly dense but well-organized and efficient.

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?

For a pull operation with one optional parameter and no output schema, the description covers the core action, side effects, prerequisite timing, and a follow-up step. It could mention conflict resolution or idempotency, but it addresses the essential aspects an agent needs to call it correctly.

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%, and the parameter description already explains the 'workspace' parameter and its default. The tool description adds no additional semantic information beyond what the schema provides, so it meets the baseline but adds no extra value.

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 states a specific action ('pull'), the resource ('server changes into the local workspace'), and adds clarifying detail ('three-way merge', 'downloads knowledge files'). It clearly distinguishes from siblings like cs_push and cs_check_drift by explaining its role in syncing.

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 explicitly instructs when to run the tool: 'Run before editing and before pushing.' It also provides a follow-up action ('commit the workspace afterwards'). However, it does not explicitly name alternatives or state when NOT to use it, though the timing guidance is clear enough.

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