ssh_sync

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

With no annotations, the description fully discloses behavioral traits: mutation of destination, destructive nature of delete, safe dry-run, default compression, password auth requirement, blocking on readonly/restricted servers, and timeout default. This exceeds expectations.

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 concise at 5 sentences, front-loading the purpose and then providing structured behavioral and usage details. Every sentence adds distinct value without redundancy.

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 thorough coverage of input parameters and behavior, the description does not mention what the tool returns (e.g., success message, list of synced files, error codes). Given no output schema, this is a notable gap, making it incomplete for an agent to understand the full response.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the interaction of source/destination prefixes, default push behavior, and clarifying the effects of delete and dryRun beyond the schema descriptions. It does not cover all 10 parameters in depth (e.g., exclude, checksum), but the additional context justifies a 4.

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 the verb 'synchronizes' and the resource 'files or directories between local and remote using rsync over SSH', distinguishing it from sibling tools like ssh_download, ssh_upload, and ssh_deploy. It is specific and unambiguous.

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 detailed usage instructions, including the prefix convention, default push behavior, and options for delete/dryRun. However, it lacks explicit guidance on when to use this tool versus alternatives like ssh_download or ssh_deploy, which are present in the sibling list.

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