teleport_to

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

With no annotations, the description bears the full burden of behavioral disclosure. It states the core action but does not discuss potential side effects, success/failure conditions, whether rotation is in absolute terms, or any safety considerations. This leaves the agent without critical behavioral context.

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, succinct sentence that conveys the essential purpose without redundancy. It is appropriately sized for the tool's simplicity and is front-loaded with the key action.

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?

Given the lack of annotations and output schema, the description is too minimal. It does not address potential issues like invalid coordinates, collisions, or the result of the operation. For a tool that teleports the bot, this missing behavioral context leaves the agent under-informed for safe invocation.

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 baseline is 3. The description adds minimal semantic value beyond the schema, only reiterating that rotation is 'optional'. It does not explain coordinate semantics (e.g., absolute vs relative) beyond what the schema already states.

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 ('Teleport'), the resource ('the bot'), and the parameters ('specific coordinates with optional rotation'). It distinctly differentiates from siblings like fly_to (which implies movement) and look_at (which handles rotation), making the tool's purpose 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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that teleportation is instantaneous as opposed to fly_to's smooth movement, nor any prerequisites or exclusions. The context only implies usage by the name 'teleport_to'.

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