Market prices

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

readOnlyHint=true and openWorldHint=true already tell the agent this is a safe external read, so the description's job is lighter. It adds the default location and the history/depth defaults, but says nothing about rate limits, data freshness, or failure behavior for unknown item names or structures.

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 front-loaded sentence that leads with the returned data and then the configuration options. The parenthetical location list is long but informative; nothing is redundant enough to cut.

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 usefully enumerates the return fields (best buy/sell, spread, order counts, volumes, optional history and depth) and covers the 20-item cap and defaults. Only minor gaps remain, e.g. item-name fuzzy matching nuance and behavior for invalid locations.

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 coverage is 100%, so the baseline is 3. The description still earns extra credit for 'location' by explaining it accepts not just city names but 'any region/system/station name, or a structure id' — meaning the schema's terse 'Market location' string does not convey.

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 resource (market prices) and enumerates exactly what is returned: best buy/sell, spread, order counts, volumes. An agent can tell it apart from wallet/market_orders in practice, but the description never names a sibling or explicitly excludes anything, so it falls short of a 5.

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 context is implied by the defaults and location options ('default Jita 4-4', history default true), but there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as market_orders or appraise for related pricing work.

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