Import a setlist from the vault

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description discloses creation behavior, skipping logic, dry-run capability, and dependency on external vault path. It provides context that annotations alone do not.

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 dense but efficient, front-loading the main action. Each sentence adds value, though slightly long. It uses clear formatting with capitalization for key terms.

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 no output schema, the description explains the return value (resolved note path, lists of built/skipped tracks). It covers prerequisites and dry-run mode. Could mention whether operators are created anew or updated, but overall 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% (all 3 params described). The description adds meaning by explaining the note parameter's structure (frontmatter fields) and how the name is resolved, and that parent_path defaults to /project1. This enhances the schema's documentation.

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 reads a setlist note and builds scenes by creating operators in TouchDesigner. It specifies the data formats (frontmatter tracks/scenes) and distinguishes from siblings like setlist_runner for skipped scenes.

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 when to use (pre-stage visuals) and when not (preset-only/cue-only scenes, which should be handled by setlist_runner). It also mentions using dry_run for validation. Prerequisites like configured vault path are noted.

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