Pull remote changes

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

With no annotations, the description carries the full burden and does well: it discloses that this is a merge/mutation of the local workspace, that knowledge files get downloaded, and that it writes a sync stamp at .mcs/cs-sync.json, plus a recommended commit to preserve history. It omits auth prerequisites and conflict/failure behavior, which keeps it from a 5.

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?

Front-loaded with the core action, then layered sequencing and side-effect notes; nearly every clause carries information. It is dense but not padded, though the parenthetical and stamp path add a little length.

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 no-annotation, no-output-schema, single-param tool, the description covers purpose, ordering, side effects, and the sync-stamp consequence, which is enough to invoke it correctly. Only failure modes and auth/permission expectations are left unstated.

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 single workspace parameter is fully documented there, including the CPS_WORKSPACE default. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('three-way merge of server changes into the local workspace') and adds the concrete side-purpose of downloading knowledge files. An agent can distinguish it from cs_push and related sync siblings without opening any schema.

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?

Gives explicit sequencing guidance ('Run before editing and before pushing') and ties the tool to cs_check_drift via the sync stamp, which tells the agent why and when it matters. It stops short of naming an explicit when-not-to-use or a direct alternative, so it lands at 4 rather than 5.

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