Scaffold a starter vault

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

The description details writing behavior, skipping existing files, and the overwrite option. It adds context beyond annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by explaining file creation. Could mention if folders are created, but still clear.

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 covering purpose, behavior, and usage, all front-loaded. No unnecessary words.

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 simple tool with one optional parameter and no output schema, the description covers purpose, behavior, prerequisites, return values, and usage context completely.

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 covers 100% of parameters, so baseline is 3. The description adds minimal extra context beyond the schema's description, mostly reiterating the overwrite effect.

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 populates an Obsidian vault with a starter layout and examples, distinguishing it from sibling tools like save_recipe_to_vault and import_setlist by specifying it's a first-time setup.

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 says to run once when first setting up a vault, before other tools, and notes the prerequisite TDMCP_VAULT_PATH. Explains behavior with existing files and the overwrite parameter.

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