rba_teleport_to_place

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic action and that joining a server job is optional. It does not mention prerequisites, side effects (e.g., leaving current server), or what happens on success/failure. This is a significant gap for a mutating operation.

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, front-loaded sentence that conveys the core purpose efficiently. No filler or redundant words. Every phrase 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?

Given the lack of annotations and output schema, the description is too sparse. It does not clarify the behavior of 'target' (all vs first vs position), the role of 'timeoutMs', or what the return value/call outcome looks like. For a tool with 4 parameters, this is incomplete.

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. It adds meaning for placeId (the target place) and jobId ('public server job'), but fails to explain the 'target' parameter (all/first/position) or 'timeoutMs' (how/when it applies). Most parameters remain semantically opaque.

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 local player to a Roblox place'. It uses a specific verb (teleport) and resource (place), and distinguishes itself from sibling teleport tools (rba_teleport_to_position, rba_teleport_to_part) by focusing on places. The optional server job is also mentioned.

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?

Usage is implied by the purpose: use this when you need to teleport to a Roblox place. However, there is no explicit differentiation from sibling tools like rba_teleport_to_position, nor any mention of when not to use it. No alternatives are named.

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