coppelia_motion

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

No annotations are provided, so the description carries the full behavioral-disclosure burden. It usefully states that planning returns a path and never applies it to robot joints, but it does not say whether operation='ik' mutates robot state, what permissions are required, what happens on failure, or how headless mode affects 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 compact and front-loaded, with no filler text. The dense inline parameter listing is efficient but reads more like a schema summary than structured usage guidance.

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 16-parameter motion tool with no annotations, no output schema, and zero schema description coverage, the description is insufficient. It leaves several parameters undocumented and does not explain the return path format, error cases, or the side-effect profile of the IK operation.

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 16 parameters. The description maps 12 parameters to the 'ik' and 'plan' operation modes, which adds useful grouping beyond the bare schema, but it omits damping, iterations, headless, and does not explain the meaning or allowed values of constraints, method, or algorithm.

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 states that this tool provides typed motion operations and enumerates operation='ik' and operation='plan' with associated parameter sets, so an agent can tell it handles inverse kinematics and motion planning. It does not distinguish this tool from siblings such as coppelia_trajectory or coppelia_step.

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?

It provides operation-specific parameter usage for 'ik' versus 'plan' and notes that planning returns a path without applying it to robot joints, which implies when to choose plan versus execution. However, it gives no explicit when-to-use guidance versus sibling tools, prerequisites, or exclusions.

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