Browse vault library

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

Discloses read-only nature, local disk access, return format (flat items + per-category counts), and preconditions (TDMCP_VAULT_PATH). Adds value beyond the readOnlyHint and openWorldHint annotations.

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?

Two sentences, front-loaded with key info (read-only, what it lists), no wasted words, well-structured.

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 purpose, filtering, preconditions, and return structure (items + counts). With output schema present, no need to describe return values further. Complete for a browse tool.

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?

Adds context beyond schema: explains 'all' lists every known category, query is case-insensitive substring on title/tags, and filtering via kinds and query. Schema coverage is 100% but description enriches understanding.

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 it lists vault items (recipes, shaders, etc.) with metadata, specifies it is read-only, and distinguishes from siblings like browse_library and list_recipes by describing a broader scope.

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: read-only, no TD connection needed, requires configured vault path. Implicitly tells when to use (browsing library) but does not explicitly exclude alternatives like search_operators.

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