td_list_media_assets

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety profile is clear. Description adds that it scans a directory and returns paths usable with specific node types, which provides context beyond 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, each adding value. First sentence states the action and resources, second clarifies the output format and usage. No wasted words.

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?

Simple tool with one optional parameter and clear purpose. Description covers what it does, what it returns, and default behavior. Output schema exists (though not detailed here) but description suffices for correct invocation.

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% with description for the 'folder' parameter. Description adds valuable context: optional, defaults to current .toe folder, and clarifies the scanning scope. No hidden parameters or ambiguity.

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?

Specific verb 'Scan a directory' and resource 'usable TouchDesigner media files' with explicit file types (video, audio, images, geometry). Returns relative paths for use with specific operators (moviefileinTOP, fileinSOP, audiofileinCHOP), distinguishing it from sibling tools that create, delete, or manipulate nodes.

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?

Description implies usage for discovering media files in a directory, but lacks explicit when-to-use or when-not-to-use guidance compared to siblings. No mention of alternative tools for more complex asset management or filtering.

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