Get Steam inventory value

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description adds one genuinely useful behavioral fact — that the value is an *estimate* rather than an exact figure, and that only top items are returned — but says nothing about latency, rate limits, or what happens when the listing has no inventory data.

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?

Two sentences, front-loaded with the core action and no filler. Minor redundancy in repeating 'Steam' three times, but nothing superfluous.

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 read-only tool with annotations covering safety and no output schema, the description gives enough to call it but omits real ambiguities: app_id is optional yet the description implies a single game, and the multi-game or no-game behavior is unexplained. Adequate, but with visible gaps.

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%, so all three parameters (item_id, app_id, currency) are already documented with description and enum values. The description only loosely echoes app_id via 'for one game' and does not mention the currency parameter, so it adds little beyond the schema's baseline.

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 ('Estimates the Steam inventory value of a Steam listing') plus scope ('for one game, with the most valuable items'). An agent can distinguish it from generic siblings like market_get_item, though no sibling is explicitly named or ruled out.

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?

'Useful when comparing Steam listings by what their inventories are worth' gives a clear selection context for the tool. It stops short of naming an alternative (e.g. market_get_item) or stating when not to use it, so it is context without exclusions.

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