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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful scope context (nearest people, nearby objects, restricted zones) but says nothing about whether results are a live snapshot, conditional on permissions, or whether any content can be omitted.

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 dense sentence that front-loads the most important observation (your room and position) before the peripheral detail. The list is somewhat run-on but every clause maps to a returned element, so little 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?

With no parameters and no output schema, the description is the sole source for what this perception tool returns, and it thoroughly enumerates the observable elements. Only the freshness/liveness of the snapshot and any formatting details are left unspecified.

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, so there is nothing for the description to disambiguate. Baseline of 4 applies for a parameterless tool.

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 enumerates exactly what the tool observes: the current room, your position and facing, nearby people and their speech, doors, nearby objects, and restricted zones. It reads as a noun list rather than a verb+resource, but the scope is unambiguous. It does not explicitly distinguish itself from overlapping siblings like 'camera' or 'look_blocks'.

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 guidance on when to reach for 'look' versus alternatives such as 'camera', 'look_blocks', or 'whats_new'. Usage is only loosely implied by the content list. No prerequisites or exclusions are stated.

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