coppelia_simulate

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 discloses that results include positions and proximity sensor samples and that export_path writes a .json file, but it does not disclose simulation-state side effects, whether file writes overwrite existing data, or how headless mode changes behavior.

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 short and front-loaded with the main action and return behavior. The compact 'until' schema notation is efficient, though the overall terseness leaves important parameter and behavioral gaps.

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?

This is a comparatively complex tool with 7 parameters, no annotations, and no output schema. The description covers the core action and return shape but is not complete enough to explain the remaining parameters or the full side-effect profile.

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% for 7 parameters, so the description must compensate. It adds useful syntax for 'until' and export_path and implies 'steps', but leave observe, sensors, headless, and sample_every completely undocumented.

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 and resource: 'Step CoppeliaSim N times', with the stopping condition 'or until a diagnostic issue'. The batch-stepping scope distinguishes it somewhat from a single-step sibling, but it does not explicitly contrast itself with coppelia_step or coppelia_sensors.

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 description implies usage through 'N times' and the 'until' diagnostic condition, suggesting this is for multi-step simulation with an early stop. However, it gives no explicit guidance on when to choose this over coppelia_step, coppelia_sensors, or other siblings, and no alternatives are named.

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