foundry_move_token

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

Beyond the annotation readOnlyHint=false indicating mutation, the description adds no detail about side effects, token identification, animation behavior, or required scene context. Since annotations provide minimal coverage, the description carries the burden and fails to disclose these.

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 clear sentence with no filler; it is appropriately compact and front-loaded. Every word earns its place.

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 tool with 9 parameters, no output schema, and minimal annotations, this one-line description is grossly incomplete—it omits token identification, scene targeting, animation options, and expected return behavior.

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 only 22%, with only userId and clientId briefly described. The description does not explain x/y coordinates meaning, the difference between name and uuid, animate, waypoints, or sceneId, leaving most parameters ambiguous.

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 uses the specific verb 'Move' and resource 'token' with destination 'canvas coordinates', clearly stating the action. However, it doesn't differentiate from sibling tools like update_canvas_document that could also move tokens.

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?

No guidance is given on when to use this versus alternatives such as update_canvas_document or select_tokens, nor any preconditions like scene/selection requirements. The description provides no usage context or exclusions.

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