vmn_sync_vault

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

With no annotations provided, the description carries the full disclosure burden. It does add one useful behavioral fact — the EXERGYNET_API_KEY requirement — but it leaves the core behavior of 'sync' unexplained: whether it pushes one-way, overwrites existing vault entries, merges, is idempotent, or what side effects occur on hash conflicts. For a mutation-style operation, this is a significant gap.

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?

Two sentences with zero waste: the first front-loads the action and destination, the second delivers the essential invocation prerequisite. Every word earns its place.

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 low complexity (2 params, 1 required), the lack of annotations and output schema means the description must explain operation effects, and it does not. An agent cannot tell whether syncing updates an existing vault object, creates a new one, overwrites, or how to verify success. The env var disclosure is helpful but insufficient for a remote-mutation operation.

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 the baseline of 3 applies. The schema already fully documents both parameters, including the SHA-256 root hash semantics for xlmp_root and the default for intent. The description merely echoes 'local memory object' without adding any parameter-level detail beyond the schema.

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 names a specific verb ('sync'), a specific resource ('local memory object'), and a specific destination ('ExergyNet LNES-17 vault'). This distinguishes it from the sibling tools — none of which describe syncing to a vault — and there is no tautology with the tool name.

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 offers no guidance on when to choose sync over the sibling tools, particularly vmn_ingest or vmn_ingest_file, whose purposes overlap somewhat with pushing data into the system. The env var note is a prerequisite, not usage guidance — it says nothing about when or when not to call this tool.

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