import_urdf

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

No annotations are supplied, so the description alone must disclose side effects. It only says the robot is imported into the scene; it does not mention scene mutation, overwrite behavior for prim_path, coordinate frame/units for position, or whether the import is reversible. This is minimal behavioral disclosure for a scene-changing tool.

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 compact, front-loaded with the main purpose, and uses a short Args section. Every sentence adds information and nothing is redundant with the schema.

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?

For a tool that mutates the scene and has no annotations, important context is missing: units and coordinate frame for position, behavior if prim_path already exists, and any preconditions on the URDF file. Even if an output schema exists, these input and environment semantics are not covered, so the description is not fully complete.

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 0% and command_id/idempotency_key are absent from the description, but the description does give plain-language meanings for urdf_path, prim_path, and position, adding value beyond the bare JSON schema. However, it omits semantics for the two remaining parameters and doesn't clarify the expected format of position beyond '[x, y, z]'.

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 opening sentence names a specific verb ('Import'), the resource type ('URDF file'), and the destination ('into the scene'), which distinguishes it from generic creation tools like create_object or create_robot. Even without explicit sibling comparison, an agent can tell this is for loading URDF-based 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?

There is no guidance about when to choose this tool over siblings such as load_usd, create_robot, or open_stage. No prerequisite conditions or exclusions are provided, so an agent must infer the appropriate context from the name and one-line description.

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