ssh_sync

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It says 'incrementally sync' and 'via rsync over SSH', which hints at the transfer mechanism, but it does not warn about potential destructive effects (e.g., overwriting files, deletion when delete=true), authentication requirements, or what happens on failure. The risk profile of a sync tool is significant, and this one-liner does not surface it.

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 single, front-loaded sentence that packs a clear verb, resource, and mechanism into minimal words. There is no redundant language or repetition of the tool name. Every phrase earns its place.

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?

Despite having 15 parameters, 4 required, and no output schema, the description gives no information about return values, error handling, prerequisites (like an active SSH session), or when to prefer this over siblings. The complexity of the tool warrants more contextual detail than a single sentence. The description is not sufficient for an agent to confidently invoke this tool in all reasonable scenarios.

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 73%, and most parameters have their own descriptions. The tool description adds no per-parameter information, but it does clarify the overall local-remote split (one local side, one remote target), which helps interpret source/destination. Since coverage is neither high nor low, a baseline 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 states a specific verb ('sync'), a specific resource ('files or directories'), and a specific mechanism ('local rsync over SSH'). It also scopes the operation to one remote target, which distinguishes it from sibling tools like ssh_scp (one-off copy) and ssh_exec (command execution). The purpose is immediately clear.

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. It does not mention that one-off copies should use ssh_scp, or that this tool is suited for incremental/backup scenarios. The description lacks any 'when to use' or 'when not to use' context, so the agent must infer usage from the name and schema.

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