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

With no annotations, the description carries the full burden and does disclose meaningful behavior: asks with zero answers are omitted, sample asks (by is_sample or specific titles) are filtered unless include_samples is true. It does not mention auth requirements or ordering, but the filtering/omission semantics are unusually well documented for an annotation-free tool.

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 pricing facts are stated two or three times ('Poll unlock $1. Asker posts $1–$5. Reader unlock $1' appears near the top and again at the end), and field-pricing musings interleave with the actual listing behavior. It is repetitive and not front-loaded around what the call does.

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 and no annotations, the description does describe the return shape (topics plus items, with inventory seed/operator/product) and names relevant response fields (price_cents, unlock_cents, deposit_cents, reader_unlock_cents). It conflates pricing meaning with data shape, but an agent has enough to interpret the response.

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 single parameter include_samples is undocumented in the schema (0% coverage), so the description must compensate. It does: sample asks 'are omitted unless include_samples is true,' which fully explains the parameter's effect beyond the bare boolean type.

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 opening line gives a clear verb+resource ('List every topic on the buyer shelf') and even enumerates what a topic contains (seed polls, operator demos, the paid-ask product). However, the core purpose is quickly buried under pricing economics, and it doesn't sharply distinguish this listing from siblings like list_polls or list_open_asks beyond one routing sentence.

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 offers one explicit route ('Call list_open_asks to answer those') for zero-answer asks and explains when sample asks appear (include_samples). But it never states when to prefer this tool over list_polls or list_open_asks generally, leaving usage largely implied.

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