Sync presets with the vault

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

Annotations already indicate non-read-only, non-destructive, and open-world behavior. The description adds the requirement for TDMCP_VAULT_PATH and notes that export produces diffable/shareable markdown. While it does not detail import side effects (e.g., overwriting), the annotations cover safety and the description provides enough context for expected 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 extremely concise: two sentences front-loaded with the core purpose, followed by a necessary environment requirement. No filler or redundant wording. It 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?

For a tool with two actions (export/import) and no output schema, the description covers the main intent and setup. It omits details like import merge behavior or error states, but given the annotations and clear purpose, it is largely complete. The agent can infer expected outcomes from the action labels.

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 baseline is 3. The description adds marginal value by clarifying 'COMP's manage_presets snapshots' and mentioning 'diffable, shareable' for export, but does not significantly augment the schema's parameter descriptions. The parameter semantics are adequate without being enriched.

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's dual purpose: exporting COMP presets to a markdown note and importing from note back to TD. It uses specific verbs (export/import) and resources (COMP's manage_presets snapshots), and the high-level action distinguishes it from siblings like 'manage_presets' which likely handles internal preset management only.

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 what the tool does but provides no explicit guidance on when to use vs. alternatives (e.g., 'manage_presets'). It implies usage for syncing with vault but does not state exclusions or prerequisites beyond the environment variable requirement. The sibling list contains 'manage_presets', suggesting an overlap, but no differentiation is offered.

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