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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by enumerating the contents of the observation, which substitutes for the missing output schema, but says nothing about cost of view=full, output size, or freshness of the snapshot.

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 compact sentence with the content list front-loaded and no filler. The comma-separated enumeration is slightly unstructured but nothing 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?

For a read-only perception tool with fully documented parameters and no output schema, listing what is observed is the essential missing piece, and the description supplies it. Only minor gaps remain (context cost of full view, snapshot timing).

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%: view, radius, and api_key all carry descriptions with defaults and tradeoffs (e.g., 'at most 12 for view=full'). The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 names a specific verb (see) and enumerates the exact resources returned: health, hunger, inventory, time, nearby agents/mobs, useful blocks, and a ground map. It is clearly a perception/read tool, easily distinguished from siblings like mine, attack, or move.

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 call this versus alternatives, no mention of calling it before acting (e.g., before mine or goto), and no advice on choosing views to conserve context. Usage is only implied by the nature of the tool.

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