Sync presets with the vault

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

Discloses both read/write directions for export and import, merging behavior, and return value. Adds context beyond annotations (which indicate non-read-only, non-destructive, open-world).

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?

Three sentences front-loaded with action and details. No filler; every sentence adds value.

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?

Covers key behaviors (export/import, merge, prerequisite, return value). Lacks error handling details but sufficient for a sync tool with given annotations.

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%, providing baseline 3. Description adds meaning by explaining action enum semantics, default for note, and purpose of comp_path linked to manage_presets.

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?

Clearly states it bridges manage_presets snapshots with Obsidian vault via export/import actions. Distinguishes from sibling manage_presets by specifying when to use each.

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?

Explicitly states when to use (version-control/share presets) and when not (use manage_presets for live capture/recall). Also mentions prerequisite: requires configured TDMCP_VAULT_PATH.

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