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

Adds substantial context beyond the readOnly/destructive hints: the status vocabulary (recorded, empty, unknown, not_indexed, unavailable), null semantics for unknown totals, the 50-item page cap, the fact that observation IDs are index-scoped and require rediscovery after reindexing, plus an explicit untrusted-data warning against prompt injection from item names.

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?

Purpose is front-loaded and every sentence carries information, but the middle section is written in a dense, telegraphic style that packs status values, null rules and pagination into single clauses, which slightly raises parsing cost.

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 an output schema present, the description supplies exactly the missing operational context: data shape (item IDs, counts, slots, names, enchantments), nested path drilling, pagination mechanics, index volatility and trust boundaries. Nothing an agent needs to call it correctly appears absent.

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 only 20%, so the description carries most of the burden and does so for the non-obvious parameters: item_path gets its nested-shulker usage, include_saved_data is tied to limit=1 for raw components/tags, and pagination is explained via nextOffset with unchanged arguments and the 50 cap. limit and offset defaults themselves are left to the schema.

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?

States a specific verb and resource: reading the saved contents of a single public storage observation from Find search/history. The phrase 'without scanning raw worlds' separates it from the search_world_find family, and 'one ... observation' separates it from list-shaped siblings.

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?

Establishes the usage context clearly (resolve saved inventories on demand rather than scanning raw worlds) and gives the nested-container procedure via item_path. It does not name a sibling alternative or state when not to use it, so it falls short of the top score.

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