coppelia_scene

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

With no annotations at all, the description carries the full burden, and it does deliver the key hazard: load stops the running simulation and replaces the current scene. It omits other load-bearing behavior such as whether save overwrites an existing file, what happens if the path is invalid, and what the call returns.

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 sentences and a terse param list, with the core purpose and hazard front-loaded ahead of parameter notes. The telegraphic 'action: save|load' style is compact and earns its space, though the sentence fragments read slightly as notes rather than prose.

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 3-parameter, annotation-free mutation tool with no output schema, the description covers purpose, one parameter constraint set, and the destructive side effect of load, but leaves headless undefined and says nothing about save semantics or failure modes.

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 0%, so the description must compensate. It documents the two required parameters with useful constraints ('action: save|load', 'path: absolute .ttt path') that the bare string schema does not convey, but leaves the third parameter (headless) completely undocumented in both schema and text.

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 pair and resource ('Save or load a CoppeliaSim scene') plus the discriminating parameter values (action: save|load), so the agent can distinguish it from siblings like coppelia_import_model or coppelia_step. It stops short of explicitly saying how it differs from related scene-importing tools.

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?

Usage is only implied: save vs load is selectable via the action field, and the destructive nature of load hints at caution. There is no explicit 'use this when...' guidance and no mention of when to prefer coppelia_import_model or coppelia_import_floorplan over loading a .ttt scene.

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