node_sync

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

With no annotations supplied, the description carries the full burden, and it does meaningfully well: it discloses that 'scoped grants' are required, that each file commits atomically, and that extra destination files are retained (i.e., this is not a mirror/delete sync). That retention note is a genuinely important behavioral trait an agent could not infer from the schema; the gaps are failure/rollback behavior and overwrite semantics for conflicting files.

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?

A single well-formed sentence with the primary action front-loaded and the behavioral caveats in a subordinate clause. Dense but every clause carries information; no filler or repetition of the tool name.

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?

For a 7-parameter mutating tool with no annotations and no output schema, the description covers the highest-risk unknowns: privilege scoping, atomicity, and the fact that destination extras survive. It stops short of describing what the result looks like or what happens on partial failure, but the critical decision inputs are present.

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 schema already documents all seven parameters including node identifiers, direction enum, exclude globs, tx_id reuse semantics, and as_root. The description adds essentially no parameter-level meaning beyond what is already structured, so the baseline of 3 applies.

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 gives a specific verb and resource: 'Synchronize a directory between the Host and a node', with the direction implied by the Host/node framing. It does not explicitly differentiate itself from the sibling node_transfer or node_read_file, so an agent must infer that this is the bulk-directory operation.

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 word 'directory' implies this is for whole-directory synchronization rather than single-file operations, which weakly routes an agent away from node_transfer/node_read_file. However, there is no explicit when-to-use, when-not-to-use, or named alternative, and no guidance on push vs pull selection beyond what the schema enum already says.

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