Read or update the artist's standing style memory

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

The description discloses that updates are field-wise merges with union+dedup for lists and overwrite for scalars, and bumps the updated date. It also states no TouchDesigner side effects. This adds significant behavioral context beyond the annotations (readOnlyHint=false, destructiveHint=false).

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 concise yet comprehensive, front-loaded with the core purpose, then elaborating on modes, behavior, and requirements. Every sentence adds value 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?

The description covers purpose, modes, update behavior, side effects, and prerequisites. The output structure for 'read' is implied by the patch schema but not explicitly stated. Given no output schema, a bit more detail would be ideal, but overall it's fairly complete.

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 baseline is 3. The description adds value by explaining the purpose of each mode (e.g., 'compact one-line context string' for show) and the merge behavior for update. This helps the agent understand parameter implications better than schema alone.

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 reads or updates the artist's style memory note in Obsidian vault. It specifies the resource (Memory/style.md) and actions (READ or UPDATE), distinguishing it from sibling tools by emphasizing it only touches the vault and has no TouchDesigner side effects.

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 each mode (show, read, update) and their use cases, such as 'show' being suitable for feeding an LLM. It also mentions the prerequisite TDMCP_VAULT_PATH. While it doesn't explicitly exclude alternatives, the unique domain makes it distinguishable.

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