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

readOnlyHint=true already tells the agent this is a safe, side-effect-free read, so the description's main value-add is disclosing the scope of what is revealed. It does that well, notably the privacy-adjacent detail that other people's typing/editing/reading states are exposed and that doors leading nowhere appear only in your own room. It does not say how far 'nearest' extends, whether output is prose or structured, or whether repeated calls are rate-limited.

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?

It is a single dense sentence whose every clause maps to a real returned field, so there is no filler. It is, however, a run-on list that opens with 'The room you are in' instead of front-loading a purpose statement, which costs a little scannability for a short definition.

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 zero parameters and no output schema, the description carries the full burden of explaining return content, and it does so field by field, while annotations cover the safety profile. The main residual gap is output format and any notion of range or refresh cadence, but for a simple perception verb this is close to complete.

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 no parameters, so the schema imposes no semantic burden and the baseline applies. The description correctly implies a parameterless snapshot rather than hinting at any hidden selectors or filters.

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 a 'look' yields: room, position/facing, dollar balance, nearby people and their activity, doors, loose bills, nearby objects, and restricted zones. That is a specific, recognizable perception-snapshot resource, distinguishable from inventory (your items) or look_blocks (block-level detail). It never states the verb explicitly, but the field list makes the purpose unambiguous.

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 when-to-use guidance and no mention of alternatives, even though siblings like look_blocks, inventory, room_settings, and find_rooms clearly overlap in what they reveal. An agent must infer from the field list alone that this is the general ambient-perception call rather than a targeted query.

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