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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds genuinely non-redundant context: results are sorted by demand, and the resource is 'free, no key' (no authentication required). It stops short of describing return shape, page size behavior, or how 'most wanted' is computed.

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 compact sentences with no filler, and the core purpose plus sort order are front-loaded before the seller-oriented framing. Efficient, though the 'Sellers:' clause is marketing-flavored rather than operational.

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 simple read-only list tool with no output schema and no required params, the description covers purpose, ordering, and auth. It leaves the category filter's meaning and the return format undocumented, which is a modest gap for a 2-param discovery tool.

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 0% and the description adds nothing about the two parameters. The category enum's ten values and the limit param are only inferable from the schema's type/enum fields, so the description does not compensate for the coverage gap, though the parameter names are fairly self-explanatory.

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 recognizable resource – unmet demand ('what agents want and cannot find yet') – and its ordering ('most wanted first'), which an agent can distinguish from siblings like wish, vote_wish, and fill_wish. It never uses an explicit list verb or names a sibling, so it stops short of full differentiation, but the content is clear.

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' gives directional context for when the tool matters to a seller, implying usage. However, it never contrasts against alternatives such as wish (post a demand) or vote_wish (upvote one), and gives no explicit when-not guidance.

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