Bind a Text DAT to a vault note

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

The description adds significant behavioral context beyond annotations: it clarifies side effects (node creation, reading the note, no writing to vault) and describes return values (DAT path, resolved note, file path, sync status). With minimal annotations (only readOnlyHint, destructiveHint, openWorldHint), the description compensates well.

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 and well-structured: it starts with the core action, then explains side effects, usage, return values, and prerequisites in clear, non-redundant sentences. Each sentence adds necessary information.

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 complexity (4 parameters, no output schema), the description covers all essential aspects: purpose, side effects, return values, prerequisites, and even downstream integration (wire into Text TOP). It leaves no major gaps for agent comprehension.

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 description coverage is 100%, but the description adds value by providing real-world usage context (e.g., 'lyrics, poetry, any text content' for 'note', and connecting to Text TOP). This enriches the parameter understanding beyond the schema's brief descriptions.

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 creates a Text DAT in TouchDesigner that reads from a vault note, using specific verbs ('CREATE') and resource ('Text DAT'). It distinguishes itself from many sibling 'create_' and 'bind_' tools by specifying the unique functionality of targeting a vault note.

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 provides a clear use case ('turning the vault into the text/lyrics source for your visuals') and mentions a prerequisite (requires TDMCP_VAULT_PATH). However, it does not explicitly state when not to use this tool or compare it to alternatives, which would raise clarity.

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