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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context by explaining what 'hub' and 'home' mean, but says nothing about failure behavior for unknown rooms, whether movement is instant, or any permissions involved.

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 tight sentence that front-loads the action and immediately enumerates the accepted values; the parentheticals clarify rather than pad. Nothing is wasted.

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 one-parameter tool with no output schema and adequate annotations, the description covers what's needed to invoke it correctly. The main residual gap is that it doesn't state what happens on an invalid destination or what the agent receives afterward.

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 0% and the single 'destination' parameter is undocumented in the schema, so the description carries the full burden. It does this well by decoding the magic values 'hub'/'home' and stating that ids or links are accepted, though it omits id/link format details.

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 states a concrete action (moving the agent) and its targets ('hub', 'home', or a room by id/link), which is clear and specific. It doesn't distinguish itself from navigation-adjacent siblings like walk_to, use_door, or leave, so an agent must infer the boundary.

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?

There is no explicit when-to-use guidance and no comparison to alternatives such as walk_to, use_door, or find_rooms. The enumerated destinations hint at usage but serve more as parameter meaning than as routing guidance.

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