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

With readOnly/idempotent annotations already covering the safety profile, the description goes well beyond them: it discloses that the headline price refreshes more often than the order-book ladders so they can briefly trail it, that sale_basis=false means the points are ask-price readings rather than real sales, that market_stats is a frozen September 2026 SCMM snapshot and is null for uncovered skins. These are exactly the caveats an agent needs to interpret the payload correctly.

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 front-loaded with the one-line summary, which is good, but the remainder is a dense run-on catalogue of every response field (some of it truncated mid-word at '`cros'), which reads more like schema documentation than guidance. The field list earns some of its place given no output schema, but it is heavier than needed.

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 no output schema, the description carries the burden of explaining return values, and it does so thoroughly for skin, price, orderbook, steam_history and market_stats, including null semantics. It is cut off mid-sentence ('`cros' for cross-market prices), so the cross-market portion is left unexplained.

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?

There is a single parameter and schema description coverage is 100%, with the schema itself explaining that itemdefid is the Steam item definition id and the rust.wiki URL segment. The prose adds nothing further about the parameter, 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 opening sentence names the resource and enumerates exactly what comes back (price, order book, history, cross-market prices), so an agent knows this is the comprehensive skin lookup rather than a narrow price call. It never names the siblings it supersedes (get_skin_price, get_skin_price_history, get_skin_collection), leaving differentiation to inference from 'Full skin detail.'

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 only implied: the field inventory makes clear this is the everything-at-once call, and 'wider ranges via /skins/{itemdefid}/history' points at a deeper history path. There is no explicit when-to-use/when-not statement and no mention that get_skin_price or get_skin_price_history are the lighter alternatives.

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