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

With no annotations, the description carries the full burden, and it does disclose useful traits: it is free, results are ranked by ask-count and recency, and entries close automatically once answered. However, it never says what a returned need record looks like, whether listing is paginated beyond `limit`, or what permissions/registration (`register`, `claim_status`) are required to fill one.

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 front-loaded sentences: what it is, that it's free, how to fill one, and when it closes. Dense but nearly every clause carries information. Minor cost: the telegraphic 'Free.' fragment and the packed `new_entity` clause read as notes rather than prose.

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 3-parameter, no-output-schema read tool it covers purpose, ranking, cost, and the follow-up mutation path reasonably well. The gaps are the undocumented `limit` and the absence of any indication of what a returned need record contains, which matters since the agent must decide whether it can fulfill one.

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%, with `kind` and `market` already described in-schema; the description reinforces those by naming the two need types. The `limit` parameter is undocumented in both schema and description, and the ranking semantics hinted at ('how many asked and how recently') are not tied to any parameter or ordering control.

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 concretely what the resource is: unmet demands ('phrases and searches with no match, unknown barcodes') ranked by frequency and recency. The verb is implicit (this is a ranked list of open needs), but the content is specific enough to separate it from siblings like `search` or `add_proof`, which it names.

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 gives a concrete trigger for acting -- 'Fill one when you have the item in hand or can open its own page' -- and routes the agent to the correct sibling, `add_proof`, with the exact payload shape. It also notes the cost ('Free') and lifecycle (self-closing). What's missing is an explicit 'when not to use this' or how it relates to `query`/`lookup_barcode` for items that do exist.

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