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

Beyond the read-only annotations, the description discloses that prices are current-station-only, that amounts are NET after sales tax, and that results are capped at 200 rows. These details materially affect how an agent interprets and relies on the returned 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?

The description is front-loaded and efficient, with the core purpose, filters, scope limit, and sibling alternatives all stated clearly. It repeats the category list already present in the schema, which is mildly redundant but still usable for quick routing.

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 must carry return-value context, and it does so by stating that results include prices, item names, and net after-tax amounts. It also gives a row cap, though it does not describe the exact response shape or pagination behavior.

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 q, tier, category, and bearer are already documented in the schema. The description reinforces the category values and search semantics but does not add parameter syntax or constraints beyond what the schema already provides.

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 states a specific verb-resource pair: it returns station market prices for the current sector, including item names and net proceeds after sales tax. It also explicitly distinguishes itself from get_price_history, get_module_listings, and trading tools like buy/sell, so an agent can identify its scope without opening the schema.

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?

It gives explicit routing: use get_price_history for prices over time, get_module_listings for player-offered used modules, and buy/sell/sell_all/place_orders to trade. The filter parameters and 200-row cap further clarify when and how to use this tool.

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