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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real semantic context beyond that: prices are denominated in priceUsd, and external sellers carry no Agent Trust Score or Proof of Outcome merely from listing. It does not describe volume, pagination, or freshness of the listing.

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 core statement is front-loaded, but several sentences are loose or puzzlingly negative, e.g. 'It is not a new Paylyte product' and the repeated 'Read that price before you buy,' which read as filler relative to the tool's purpose. Tighter phrasing would earn more per sentence.

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 zero-parameter, read-only list tool with no output schema, the description supplies the key return semantics an agent needs (USD pricing, external-seller caveats). Missing pagination/result-size behavior keeps it short of full completeness.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline is 4. The description correctly adds no fake parameter guidance and instead spends its words on result semantics.

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 and resource: 'list every live paid offering,' and clarifies the scope includes both Paylyte products and external sellers. It distinguishes itself from siblings only implicitly (the 'read that price before you buy' line gestures at buy_live_offering), so it is clear but not sharply differentiated.

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 only usage guidance is the implied 'read that price before you buy,' which suggests this precedes a purchase, but the description never explicitly states when to use this versus buy_live_offering or get_track_record. Usage context is present but left to inference.

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