List tools people want that don't exist yet

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description does add genuine behavioral context beyond that: results are pre-aggregated rather than raw, requesters are anonymous, and ordering is by frequency. It omits pagination behavior, the default limit of 20, and what fields a 'need' record contains.

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?

Two tight sentences, and the one that matters (aggregated, anonymous, frequency-sorted) comes first. The indie-maker framing is slightly promotional but still earns its place by signaling the intended audience. Nothing is redundant.

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, side-effect-free read tool with full schema coverage and no output schema, the definition covers purpose, ordering, and audience. The only real gap is that no output schema exists and the description does not say what a returned need looks like beyond a request count ordering.

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 100% and all three parameters carry their own descriptions including the default and the maximum. The description adds no parameter detail at all, which is acceptable when the schema does the full job, so the baseline of 3 applies.

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 resource (unmet needs) plus two meaningful qualifiers: aggregated/anonymous and sorted by request frequency. That is far more than a restatement of the name. It stops short of distinguishing itself from the sibling log_unmet_need (the write counterpart) or search_tools, so sibling differentiation rests on the name alone.

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 line 'Useful for indie makers looking for product ideas' supplies a motivation and implied context for calling it. However, there is no explicit when-to-use versus alternatives, no mention that log_unmet_need is how records get created, and no note about when a keyword or category filter is preferable to a plain listing.

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