Move token

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

Beyond the annotations, the description discloses that grid, walls and scene bounds are not checked, animation vs. instant jump behavior, and that the answer reports the position Foundry actually stored. This gives an agent the non-obvious side effects of the call.

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?

Three short sentences front-load the core action and then add scoping, coordinate semantics, caveats, animation behavior, and return behavior. No filler or repetition of schema 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 simple 5-parameter positioning tool without an output schema, the description covers the required coordinate semantics, optional scene resolution, coordinate caveats, animation behavior, and return value. An agent has everything needed to invoke it correctly.

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?

The input schema already documents all parameters at 100% coverage, but the description adds meaning: x/y denote the token's top-left corner in scene pixels, position is not validated against grid/walls/bounds, and animate means gliding instead of jumping. This is useful clarification on top of the schema, though not every parameter is re-explained.

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 first sentence names the operation ('Put a token at a new position') and its target resource (token on the active scene or sceneIdentifier). This clearly distinguishes move-token from sibling update-token and set-targets.

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 gives clear context: tokens are placed in scene pixels, the scene defaults to the active one unless sceneIdentifier is supplied, and x/y are top-left coordinates. It does not explicitly name alternative tools or state when not to use it, so it falls just short of a 5.

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