Connect Omniverse USD bridge

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

Annotations already declare readOnlyHint=false and destructiveHint=false, which aligns with the 'Create' action. The description adds specific scaffold contents but does not disclose additional behavioral traits like side effects, prerequisites, or impact on the current TouchDesigner session. It provides some context but not rich behavior beyond the 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?

The description is a single sentence, approximately 20 words, with the verb and resource front-loaded. It is efficient and contains no unnecessary words or repetition of the tool name or title.

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?

With 9 parameters, no output schema, and low parameter descriptions, the one-sentence description is insufficient. It does not explain return values, side effects, prerequisites, or how the scaffold integrates into the environment. The enumeration of scaffold features gives some idea, but missing critical operational details makes it incomplete for such a parametrized 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?

Schema description coverage is only 22% (2 out of 9 params have descriptions). The description must compensate but only vaguely references concepts like Nucleus, layer maps, and variant maps, without explaining specific parameters (e.g., sync_mode enum values, server_url, active). This leaves the agent under-informed about most parameter meanings and valid options.

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 uses a specific verb ('Create') and resource ('NVIDIA Omniverse/USD stage sync scaffold'), and enumerates distinct components like Nucleus/stage metadata, layer maps, variant maps, and live-session notes. This clearly differentiates it from other bridge tools in the sibling list (e.g., Unreal, Blender) by naming the Omniverse platform and USD format.

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 clearly implies usage context by naming Omniverse/USD and scaffold components, making it evident when to choose this tool. However, it lacks explicit 'when not to use' guidance or mention of alternatives, such as other bridge creation tools, so it falls short of a 5.

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