coppelia_import_model

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

No annotations are provided, so the description carries the full behavioral burden. It indicates that importing creates roots and reports joint counts, but it omits important side effects such as whether it mutates the current scene, how existing objects are handled, what happens on failure, and what headless mode changes.

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 tightly written sentence that front-loads the action and supported formats, then states the reported outputs. No wasted 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?

For a mutation-capable import tool with six undocumented parameters, no annotations, and no output schema, the description is too thin. It gives the file formats and a partial return summary but lacks sufficient behavioral and parameter context for confident invocation.

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% across six parameters. The description mentions file formats relevant to path but does not explain scale, headless, position, orientation, or package_root, leaving most parameters undocumented in both schema and description.

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?

States a specific verb (Import) and resource (URDF, SDF, STL, OBJ, or DAE files), and notes the reported outputs (roots and joint counts). It is fairly easy to distinguish from coppelia_import_floorplan, though it does not explicitly name that sibling.

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 supported file formats imply when the tool is applicable, but there is no explicit guidance on when to use it instead of coppelia_import_floorplan or other scene-building tools. No prerequisites or exclusions are stated.

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