list_nvidia_assets

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that the result combines a verified catalog with a robot library discovered from the running Isaac Sim 6.0 asset root, indicating a dependency on the live simulation state. It does not mention staleness or the relationship to refresh_robot_library, so transparency is partial.

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 purpose is front-loaded in one sentence, followed by a compact source explanation and an Args breakdown. The category list is slightly awkward but not padded or redundant.

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?

The description covers the main listing behavior, data sources, and the three user-facing parameters, and an output schema exists to describe return values. It is incomplete around the two infrastructure parameters and lacks usage guidance relative to siblings, leaving some decisions to inference.

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?

The schema has 0% description coverage, so the description compensates by documenting the category values, query's case-insensitive search fields, and max_results' valid range. This is meaningful additional semantics, but command_id and idempotency_key remain unexplained.

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 opens with a specific verb and resource: 'List NVIDIA assets that can be spawned through MCP.' It further clarifies scope by describing the combined Isaac/SimReady/Vegetation catalog and the live robot library. However, it does not explicitly distinguish this from overlapping siblings such as list_available_robots.

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 given about when to choose this tool over alternatives like list_available_robots or when to call refresh_robot_library first. The description implies the tool is for listing spawnable assets but provides no exclusions, preconditions, or alternative conditions.

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