Teleport the player character

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

No annotations are provided, so the description carries the full burden. It does not disclose whether teleporting is safe/reversible, whether it requires the player to be alive/loaded, what happens if multiple targeting parameters are supplied, or whether the change persists server-side. For a mutation tool with zero annotation coverage this is a significant gap.

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, well-formed sentence that front-loads the action and resource before listing the options. No waste, no redundancy.

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 tool takes 4 mutually-related targeting parameters with no required fields and no annotations or output schema. The description does not resolve the ambiguity of which parameter to use, the precedence if several are given, or the behavioral effects of teleporting. For a mutation tool with this complexity, the description is under-informative.

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 100%, so the schema already documents all four parameters in detail. The description only names the categories (player, coordinates, relative offset, lookAt) without adding format or precedence rules beyond the schema. Baseline 3 is appropriate.

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 (teleport) and resource (LocalPlayer's character), and enumerates the three targeting modes: a player, coordinates, or a relative offset. This distinguishes it clearly from siblings like set-player-property or fire-remote.

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 by naming the three alternative targeting modes, so an agent can infer which parameter matches which intent. However, it never states when to use teleport-player versus set-player-property, nor does it warn about mutual exclusivity of the targeting parameters.

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