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

Annotations already indicate readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful behavior beyond annotations: it clarifies that listings are player-listed, that base_id can be either a Base ID or POI ID, and that the tool defaults to the current station.

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 main action is front-loaded and the details are grouped in a parenthetical. There is some redundancy between 'ships listed for sale' and 'player-listed ships for sale', but overall the description is compact and readable.

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 filtered listing tool with strong annotations and fully documented parameters, the description covers the essential inputs and selection behavior. It does not describe the output shape or pagination, but the absence of an output schema and the simple browse semantics make this a minor gap.

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%, and the schema already documents each parameter adequately. The description mostly repeats what the schema states, such as base_id defaulting to the current station and filters for class_id and max_price. It adds little semantic value beyond that 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?

The description clearly states a specific verb and resource: browsing ships listed for sale at a base. It distinguishes this from siblings like list_ship_for_sale (which sells a ship) and buy_listed_ship (which purchases one) by specifying this is a view of player-listed ships.

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 gives clear context on how to target a station: default to current base or pass base_id as either Base ID or station POI ID, and optionally filter by class_id or max_price. It does not explicitly mention when not to use it or name alternatives, but the read-only browsing context is clear.

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