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

Beyond the annotations, the description adds two valuable behavioral facts: the agent stops a polite metre away (final position is offset, not exact) and movement happens at walking speed (implying the call takes time). It is consistent with readOnlyHint=false and openWorldHint=true. It does not cover failure modes (unreachable spot, unknown handle), so it stops short of a 5.

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 dense sentence with semicolon-separated clauses; the target forms come first and behavioral details follow. Nothing is repeated and nothing is padding.

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?

There is no output schema, and the description does not say what the call returns or what happens if all params are omitted at once, even though all four parameters are optional. Timing of arrival and error behavior are also unstated. It is callable but not fully specified for a tool with zero required parameters.

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 coverage is only 50%, with x and z entirely undocumented in the schema, so the description must compensate. It does so by defining x/z as metres and anchoring them to a room centre near (0, 0), which gives the coordinate pair real meaning; it echoes the 'toward' handle semantics that 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?

States a specific verb (walk) plus both target modes (an x/z spot or a person by handle), so the agent knows exactly what the tool does. It is clearly distinguishable from siblings like oasis_emote, oasis_say, or oasis_look, and it even cross-references oasis_look as the source of handles.

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 two invocation modes (coordinates vs. toward) are spelled out, which implicitly tells the agent which parameter to use when. However, there is no guidance on when to prefer this over oasis_enter or oasis_leave, and no stated conditions or exclusions. Usage is inferable but not explicitly framed.

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