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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's job is to add depth – and it does: data provenance (Everloot's authorized public corpus), the 3-install consensus threshold for names/pins/rates, exclusion of Wowhead rows, connectivity dependence, and explicit reporting of missing data. That is rich behavioral context beyond the annotations.

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 dense and information-rich with no filler sentences, and the core payload description is front-loaded. The clipped fragments ('No Wowhead rows.') read terse rather than wasteful, though they slightly hurt flow.

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?

An output schema exists, so return-value shape needn't be repeated; the description instead supplies the semantic rules (consensus thresholds, corpus dependency, explicit failure reporting) an agent needs to interpret results. What's missing is when-to-use routing against the many sibling page tools.

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 single itemId parameter has 100% schema description coverage ('Item id from a drop row.'), so the schema carries the semantics. The description adds nothing about the identifier's expected origin or format, which is the baseline score when schema coverage is complete.

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 states a specific resource ('One Forever item') and enumerates the exact payload: agreed name, public drop rate with kill count, and agreed map pin. This sharply separates it from sibling page tools such as npc_page, quest_page, object_page and vendor_page without needing to open any schema.

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?

It explains the consensus conditions under which a name, rate or pin becomes public, which implicitly tells the agent what will and won't be returned. However, it never states when to reach for item_page versus siblings like get_entity, search or recipe_thresholds, so selection guidance is only implied.

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