Learn the artist's house style from the saved vault corpus

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

Discloses that it writes to Memory/corpus_style.md and optionally merges into Memory/style.md, which is important since readOnlyHint=false. It also notes the env var requirement and that it is a pure filesystem operation. The phrase 'pure filesystem read' is slightly misleading given the writes, but the writes are clearly disclosed.

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 only two sentences, front-loaded with the sibling relationship and then packing in details about inputs, outputs, and prerequisites. Every clause contributes new information without redundancy.

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 the core purpose, input parameters, output files, optional merge behavior, and prerequisites. However, it does not describe the return value (especially for dry_run mode) or explain that also_patch_style_memory defaults to true, which would be useful given there is no output schema.

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?

The input schema has 100% coverage with detailed descriptions for all 6 params. The description adds value by mapping the observe families (palette, naming, recipe-shape, param-default) to the vault corpus folders and by explaining vault_path via TDMCP_VAULT_PATH. It does not merely duplicate schema details.

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 'walks the Obsidian vault corpus' and 'distils palette, naming, recipe-shape, and param-default preferences' into specific output files. It distinguishes itself from sibling learn_conventions by explicitly calling itself the 'Offline companion' and noting 'No TouchDesigner required'.

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?

Provides clear context for when to use: as an offline companion to learn_conventions, with no TouchDesigner required. It also states the prerequisite of TDMCP_VAULT_PATH or vault_path. However, it does not explicitly describe when not to use it or directly contrast with other alternatives beyond learn_conventions.

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