create_robot

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

Discloses fuzzy matching, return fields, and prim_path override behavior. With no annotations, description carries the burden and does well, though could mention if conflicting robots are replaced.

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 clear sentences for purpose, then bullet-style parameter details. Front-loaded with core purpose and prerequisites. No superfluous text.

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 moderate complexity (4 params, fuzzy matching, overrides) and presence of an output schema, the description covers prerequisites, fuzzy matching behavior, and return fields adequately for correct usage.

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?

With 0% schema description coverage, the description provides meaningful explanations for all 4 parameters: robot_type as a fuzzy search term, position as world coordinates, name as custom prim name, and prim_path as an override. Adds value beyond schema types.

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 a robot in the scene from the Isaac Sim asset library, with specific verb+resource. It distinguishes from siblings like create_object and import_urdf via the robot library source.

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?

Explicitly advises calling list_available_robots first and creating a physics scene before use, providing clear context. Does not explicitly state when not to use, but guidance is sufficient.

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