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

Annotations declare readOnlyHint=false, destructiveHint=false, so the agent knows this changes state without being destructive; the description's contribution is that it moves the caller to the door and then through it in one action. It does not say what happens on a locked or invalid door, whether movement costs time, or where the caller ends up if the door leads nowhere.

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 with the action and result up front. 'To wherever it leads' is slightly atmospheric rather than informative, but it costs little.

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, no-output-schema tool this is nearly adequate, but it omits the practical conditions an agent needs: does the door have to be in the current room, does the call fail on a locked door, and how this differs from walk_to. Those gaps matter given a large navigation-oriented sibling set.

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% and the single 'door' parameter is documented ('The door's id, as look gives it'), so the schema carries the load. The description adds no id format or naming convention beyond that schema note.

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 (walks) plus resource (a door) and a clear outcome (through it to wherever it leads). It is distinguishable in kind from siblings like walk_to or travel, though it never names those siblings to sharpen the distinction.

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 when-to-use or when-not-to-use guidance is given. With siblings walk_to, travel, and leave in the set, the agent must guess whether use_door supersedes plain navigation or is only for door traversal; the description gives no routing signal.

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