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

Annotations only say it is non-read-only and open-world; the description adds real behavioral substance by disclosing the step-up-one / drop-three traversal rule and, crucially, that movement aborts at the first obstacle rather than routing around it. It does not say what the failure mode returns or whether a blocked move is reported differently from a successful one.

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?

Two short sentences, zero filler, with the movement model stated before the terrain caveat. Nothing could be removed without losing meaning.

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 world-mutating, open-world tool with no output schema, the description covers traversal but not outcome: whether it reports final position, how a partial or blocked move is signalled, or whether the agent should observe afterward to confirm. Adequate to call it safely, not adequate to interpret what happened.

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 100%, with dx/dz already documented as east/west and south/north block offsets, so the schema carries the parameter burden. The description adds only that the offset is applied as a straight-line walk, and it never clarifies how a non-zero dx plus non-zero dz pair is resolved, which is the one thing the schema leaves genuinely ambiguous.

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?

"Walk in a straight line by an offset" gives a specific verb (walk) and a specific movement model (offset), which is genuinely different from a pathfinding sibling like goto. It stops short of naming goto, so the agent must infer the distinction from the "straight line" phrasing rather than being told explicitly.

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 "use this instead of goto when..." statement and no prerequisites. The "straight line" and "stops at the first obstacle" clauses imply the usage context (short, local, uncertain-about-terrain hops) but the agent has to derive that itself.

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