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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent already knows this mutates state non-destructively; the description's 'turns you' is consistent with that. It adds the useful note that the camera follows facing, but says nothing about whether the turn is instant, persistent, or reversible.

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, action stated first, behavioral consequence second. Zero filler.

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 5-parameter, zero-required, no-output-schema tool, the description covers the intent and the target kinds but leaves ambiguity about mutual exclusivity of the targets and what happens on an out-of-range or missing combination.

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 only 20%, so the description must carry the load, and it does name all five inputs: row, column, an optional layer ('if not your own'), a person, and a direction. It maps the parameter kinds to the target types, though it doesn't specify that row/column must be supplied together or how they interact with person/direction.

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?

Specific verb ('turns you where you stand') plus the three accepted targets (place, person, direction), and it clarifies the effect on the camera. It does not explicitly differentiate itself from siblings such as look, camera, or walk_to, so it stops short of a 5.

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?

Usage is implied by the description — orient toward something — but there is no statement of when to prefer this over look, camera, or walk_to, nor any prerequisites or exclusions. Adequate but with a clear gap.

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