Connect Omniverse USD bridge

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, providing a safety baseline. The description adds little about side effects (e.g., whether it overwrites existing scaffolding, touches external servers, or requires a running Nucleus session), so it doesn't significantly enrich behavioral 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?

A single concise sentence that front-loads the primary purpose ('Create an NVIDIA Omniverse/USD stage sync scaffold') and then lists key components. It's efficient with no filler, but the trailing list of items makes it slightly dense and could be easier to parse if 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?

Given the tool's complexity (9 parameters, no output schema), the description is too sparse. It doesn't explain the scaffold's functionality, what gets created, or how to use the parameters. The lack of any return-value info and minimal parameter explanations leave an agent without enough context to invoke it correctly.

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 only 22% (only 'name' and 'parent_path' have descriptions). The description mentions 'Nucleus/stage metadata, layer maps, variant maps, and live-session notes,' which loosely maps to nucleus_url, stage_path, layer_count, and variant_count, but it doesn't explain critical parameters like sync_mode, server_url, or active. The description only partially compensates for the low schema coverage.

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 an NVIDIA Omniverse/USD stage sync scaffold with specific components (Nucleus/stage metadata, layer maps, variant maps, live-session notes). This differentiates it from other bridge tools by focusing on scaffold creation for Omniverse, though the title says 'Connect' while the description says 'Create', which is slightly confusing.

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?

No guidance is provided on when to use this tool instead of alternatives like other 'connect' or 'create' bridges. The description doesn't mention prerequisites, exclusions, or intended scenarios beyond assuming the user needs an Omniverse/USD sync setup.

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