surface

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

With no annotations, the description carries the full behavioral burden, yet it discloses nothing about execution: whether the move is blocking, whether it uses pathfinding, whether it can fail or get stuck, permissions, or side effects. 'Surface-like' is not explained.

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 short imperative sentence with no filler, and the action is front-loaded. It is efficient, though its brevity borders on under-specification rather than tight editing.

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?

An output schema exists, so return values need not be described, and there are no parameters to cover. Still, the central ambiguity ('closest surface-like area') and total absence of behavioral detail leave an agent without enough to predict the tool's behavior.

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?

The tool takes zero parameters, and the description does not invent any. Baseline 4 applies since there is no parameter surface to document.

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?

It gives an action ('Head towards') and a target ('closest surface-like area'), so it is not a tautology of the name 'surface'. However, 'surface-like area' is vague and undefined, and nothing distinguishes it from movement siblings such as 'explore', 'thisway', 'come', or 'path'.

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 on when to use this versus the many other navigation tools ('explore', 'thisway', 'path', 'goal_coordinates'). The intended scenario must be inferred entirely from the one sentence.

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