sync_files

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

No annotations are provided, so the description carries full burden. It discloses that the tool uses rsync, requires an SSH profile, offers a dry-run mode, and that no local-to-local sync is supported. However, it does not mention whether the operation is destructive or reversible, nor does it address authentication, rate limits, or error 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 concise and front-loaded with the core purpose. The Args list is well structured. A minor improvement would be to reduce redundancy (e.g., repeating 'alternative to mount').

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?

Given the tool's complexity (5 parameters, two usage modes, required transport) and the presence of an output schema, the description covers the essential invocation logic. However, it lacks details on return value behavior, error scenarios, and what happens with existing files (overwrite? merge?). This leaves some ambiguity for agents.

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?

The input schema has 5 parameters with 0% description coverage. The description's Args section adds significant meaning: transport is an SSH profile required with no implicit fallback; mount and local_path/remote_path are two alternative path specification methods; dry_run shows what would be transferred. This goes well beyond the schema's property definitions.

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 tool syncs files between a local machine and a remote SLURM cluster using rsync. It specifies the two modes (mount vs explicit paths) and distinguishes the tool from its siblings, none of which handle file synchronization.

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 explains when to use this tool (to sync files) and provides guidance on the two alternative invocation styles (mount vs explicit paths). It also clarifies that transport is required, names an SSH profile, and rejects 'local' as invalid. However, it does not explicitly state when not to use this tool versus other tools, though sibling tools are unrelated.

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