Browse vault library

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

The description states it is read-only, requires no TouchDesigner connection, reads from local disk, and returns a flat items array with per-category counts. This aligns with annotations (readOnlyHint, destructiveHint=false) and adds valuable behavioral context beyond what annotations provide.

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 two sentences plus a final requirement line, front-loaded with purpose and key features. Every sentence adds value with no unnecessary repetition.

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?

Given the tool's simplicity, the description covers inputs, behavior, and output format. However, it does not mention if there is any limit on results or pagination; this is minor given that an output schema exists but is not shown. Still, a complete description would address potential result size.

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 schema coverage is 100% and the description elaborates that 'kinds' filters by category and 'query' is a case-insensitive substring filter on title/tags, adding clarity beyond the schema alone. The description could also mention that 'all' lists every known category.

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 verb 'list' and the resource 'vault's recipes, shaders, presets, components, and setlists'. It explicitly distinguishes from sibling tools like 'browse_library' and 'list_recipes' by specifying it lists vault items with title/tags/description for selection without opening notes.

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 indicates when to use ('so the agent can pick from the library without opening individual notes'), provides filter options (category and substring query), and notes the prerequisite (TDMCP_VAULT_PATH). It does not explicitly exclude alternative tools, but the context is sufficient. A slight improvement could be noting when not to use this tool.

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