market_price_check

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

No annotations are provided, so the description carries the burden. It does disclose the types of data returned (sell/buy stats, cheapest sellers, trade chat messages) and implies a read-only nature via 'check'. However, it omits any details about response structure, pagination, rate limits, or data refresh behavior, which would be valuable for full transparency.

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?

A single sentence that is front-loaded with the action and resource, followed by key output details. Every word contributes, no redundancy or 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?

The tool is moderately simple with 4 well-documented parameters and no output schema. The description covers the core purpose and output categories, which is largely sufficient. Minor gaps exist (e.g., exact format of trade chat messages or order ordering), but overall the description gives an agent enough to understand what the tool returns.

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 the baseline is 3. The description only restates that multiple item names are accepted ('one or more tradeable items') and does not add meaning beyond the schema. No further elaboration on parameters is needed, but also no added value is provided.

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 specifies 'Check live trading prices' for 'one or more tradeable items on warframe.market' and lists concrete output types (sell/buy stats, cheapest sellers, trade chat messages). This clearly distinguishes it from sibling lookup and state tools.

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?

The description clearly implies when to use this tool (whenever market prices are needed) and the term 'trading prices' sets it apart from item stats/other lookups. It does not explicitly name alternatives or exclusions, but the context is strong enough for an agent to select it appropriately.

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