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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely non-obvious context: values are re-priced on each view or by a daily warmer for the top 20, network-wide totals are included, and no API key is required. It omits only return-shape and ordering-stability details.

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?

The lead sentence front-loads the identity of the resource, and the following sentences add pricing behavior, page size, and auth facts. The parenthetical about re-pricing is dense but each clause carries information; slight redundancy with the title is the only waste.

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 single-optional-parameter read tool with no output schema, the description covers scale (20 per page), freshness semantics, auth requirement, and aggregate content — everything needed to call it correctly. Nothing material is missing.

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% and the single 'page' parameter is fully documented in the schema, including the 20-per-page size. The description's '20 per page' merely restates the schema, adding no new semantics — 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 states a specific resource (the rust.wiki/inventory leaderboard) and ranking rule (total value at last check), so an agent knows this lists top inventories globally rather than fetching one inventory like the get_inventory siblings. It doesn't explicitly contrast itself with get_inventory, get_inventory_snapshot, or list_inventory_snapshots, so sibling differentiation is only implicit.

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?

Usage is implied by the leaderboard framing — use this to see top-valued inventories — but there is no explicit 'use when' statement and no exclusion pointing to get_inventory for a specific player's inventory. An agent can infer the purpose but must reason about alternatives on its own.

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