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

No annotations are provided, so the description carries the full burden. It does disclose two useful behavioral facts — results are ordered by demand ('most wanted first') and no API key is needed ('Free, no key') — but says nothing about result shape, count, or how the limit parameter behaves.

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?

Three short, front-loaded sentences with no filler; the ordering rule and audience call-out each earn their place. It is slightly more promotional than informational, but nothing is wasted.

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 annotations, no output schema, and zero parameter documentation, the description should do more. It covers what the result conceptually is and the auth situation, but leaves return format and both parameters unexplained.

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 0% for two parameters, and the description never mentions limit or the category enum. With coverage that low the description is expected to compensate, and it does not; the only adjacent hint is the ordering remark, which is not a parameter explanation.

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 the resource concretely: a ranked list of 'what agents want and cannot find yet, most wanted first,' which pins down both content and ordering. The verb 'list' comes only from the tool name, and it never distinguishes itself from near-siblings like wish, vote_wish, or fill_wish, so an agent must infer the boundary.

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?

'Sellers: build one of these and buyers are already waiting' implies a usage context (supply-side discovery) but gives no explicit when-to-use rule and names no alternative tool. It hints at intent without routing the agent among the many wish-related and listing-related siblings.

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