ssh_sync

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions 'via rsync' but does not specify that the tool can delete files (via the delete parameter) or any other side effects, permissions needed, or return behavior.

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 concise sentence that conveys the core purpose efficiently. It is front-loaded and free of fluff, though it could benefit from additional context without being verbose.

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?

With no output schema, the description should explain return values or results, but it does not. The tool has 10 parameters and is moderately complex; the description lacks usage examples, return info, or any guidance on how the sync behaves (e.g., mirroring vs. incremental).

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%, so the baseline is 3. The description adds 'via rsync', which provides context but does not enhance understanding of parameters beyond the schema descriptions. It does not explain the local:/remote: prefix syntax further.

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 uses the specific verb 'synchronize' and clearly identifies the resource as 'files/folders between local and remote via rsync', which distinguishes it from sibling tools like ssh_upload or ssh_download that are one-directional.

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 provides no guidance on when to use this tool versus alternatives. It lacks any context about prerequisites, when not to use it, or how it compares to other file transfer tools like ssh_upload/ssh_download or backup tools.

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