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

Annotations already declare a read-only, idempotent, non-destructive, closed-world operation. The description adds meaningful behavior beyond that: the data refreshes about every 6 hours, skins with under 30 history points are excluded, and reference prices come from Steam's multi-year high/low history.

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 description is dense but mostly front-loaded: it lists the three categories and then defines their fields and caveats. The opening phrase repeats the title, which is mildly redundant, but the remaining detail is useful rather than filler.

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 and no parameters, the description carries the return-value burden well. It names each category and gives the fields returned for stonking/crashing and anticipated results, plus the refresh cadence and an important exclusion rule.

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 tool takes zero parameters, so there are no parameter semantics to explain. This meets the baseline for a no-parameter tool, and the description does not introduce any unnecessary parameter-like guidance.

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 the rust.wiki Insights page and clearly defines the three result categories: stonking, crashing, and anticipated skins. It is specific about counts and data meaning, though it does not explicitly distinguish itself from siblings like get_skin_price_history or find_skin_deals.

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 market-movers/Insights framing, but there is no explicit when-to-use guidance or named alternative. The agent can infer that this is for top gainers, losers, and anticipated skins, but must compare sibling names on its own.

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