Token Move

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

With no annotations provided, the description carries the behavioral disclosure burden. It goes beyond a basic statement by revealing that the operation is a REST PUT and that a WebSocket broadcast of 'map.changed' synchronizes all clients. This gives useful side-effect awareness, though it omits permission or validation details.

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 a single compact sentence that front-loads the core action and then adds the key technical/behavioral details. Every element earns its place with no redundant wording.

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?

The description gives the essential operation and a key side effect, and the output schema reduces the need to describe return values. However, for a tool with four required parameters and no annotations, it leaves gaps around parameter semantics and preconditions, so it is only minimally complete.

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%, so the description must compensate for the four parameters. It only loosely refers to 'position', which implies x and y are coordinates, but it does not define map_id or token_id, nor clarify whether x and y are absolute or relative values.

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 clearly states the action ('移动 token' = move token) and the resource being modified (token position). It distinguishes this from sibling tools like token_add and token_hp by specifying 'REST PUT position', making the intent unambiguous.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that token_add is for creating tokens or token_hp for health changes, nor does it specify any preconditions such as the token needing to exist on the map.

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