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

No annotations are provided, so the description carries the full disclosure burden. It usefully reveals sort order ('newest close first'), the return fields, and cursor-based pagination, but says nothing about auth requirements, rate limits, result caps, or what happens when none of category/item/q is supplied.

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?

Compact and front-loaded: the what, the returned fields, the parameter rule, and pagination in three tight sentences. Some of the parenthetical slugs duplicate the schema's own descriptions, costing a little density.

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 6-param, no-required, no-output-schema, no-annotation read tool, this is close to complete: it defines the payload shape in lieu of an output schema and the parameter-selection rule. The remaining gaps are edge behavior when no selector is passed and any rate/auth constraints.

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 67%, and the description compensates for the gaps: it explains item is a 'tracked item slug', q is 'free text, matched like a listing title', and cursor is the pagination handle. It adds meaning beyond the schema for the highest-ambiguity params, though category and limit go unmentioned.

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 verb+resource ('the actual sold lots behind a comps number') and immediately frames the distinction from the sibling sold_comps by positioning itself as the raw-lot view rather than the aggregate comp. It also enumerates the returned fields, so an agent knows exactly what payload to expect.

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?

Gives explicit selection guidance — 'Pass one of category, item ... or q ..., plus optional state' — and says how to paginate. It does not, however, contrast when to prefer this over sold_comps or sold_comps_batch, so the agent must infer the drill-down-vs-aggregate choice.

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