Teleport a player

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

Annotations already establish that this is a mutating, non-destructive, non-idempotent operation. The description adds useful behavioral context beyond that: the online requirement, the specific `player_offline` error, and the recommendation to check the surface first. It does not cover permission requirements or chunk-loading behavior, so it is strong but not exhaustive.

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 three front-loaded sentences with no wasted text. The target-mode constraint appears first, followed by the prerequisite and the online failure condition.

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 teleport mutation with rich schema coverage and clear annotations, the description covers the essential call requirements and one common failure mode. It could say more about permissions or what happens if the destination is in an unloaded chunk, but it is otherwise complete enough for an agent to invoke 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?

With 100% schema description coverage, the schema already carries the parameter basics. The description adds a meaningful constraint that is not obvious from the schema alone: exactly one of location, toPlayer, or worldSpawn must be provided. It also ties the get_block check to selecting safe y coordinates.

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 a specific verb and resource ('Teleport a player') and explicitly enumerates the three target modes: coordinates, another player, or a world spawn. This lets an agent distinguish it from sibling tools like locate or set_world without opening the schema.

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 gives clear contextual guidance: exactly one target mode must be supplied, the player must be online, and get_block should be used first to find a safe surface. It does not state when not to teleport or name a direct alternative tool, which keeps it 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.