vault_rsync

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

Since no annotations are provided, the description carries the full burden. It discloses a key behavioral trait: the SSH key is written to a temp file for the duration of the transfer and deleted immediately after. This is important security context. It does not mention other behavioral aspects like whether the operation is destructive or rate limits, but the key handling disclosure is sufficient for a score of 4.

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 extremely concise with two sentences, no wasted words. The first sentence packs the purpose and a key behavioral note, and the second sentence gives a usage recommendation. It is efficiently structured and easy to scan.

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 has no output schema and 7 parameters, the description covers the essential inputs and key behavior. It could optionally mention what the tool returns (e.g., success/error or rsync output), but this is not critical. Overall, it provides sufficient context for an agent to use the tool correctly.

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?

All 7 parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds meaningful extra context: the trailing slash behavior for local_path (contents vs directory sync) and notes extra_args as optional. This additional information warrants a score of 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 tool syncs a local directory to a remote host using rsync over SSH with a vault-fetched SSH key. It specifies the verb 'sync', the resource 'local directory to remote host', and the method 'rsync over SSH'. It also explicitly contrasts with the sibling tool vault_exec + python hex-encoding for deploying files, providing a clear distinction.

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 explicitly advises to use this tool instead of vault_exec + python hex-encoding for deploying files to remote servers, giving clear usage context. However, it does not elaborate on when not to use it or other alternatives, which prevents a score of 5.

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