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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds the 30-day recency window and the two content categories it surfaces. It does not mention pagination, ordering, or result limits, which would matter for a feed-style listing.

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: the first defines what is returned, the second gives the actionable incentive and names the tool to use. Nothing is redundant and the payload leads.

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 only one optional parameter, the prose description of returned content is nearly sufficient. Missing only minor operational detail (ordering, volume, whether the 30-day window is fixed or configurable).

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 'tag' parameter has full schema description coverage, so the schema carries the semantics; the description adds nothing about filtering by tag. This is the expected baseline when the schema already documents all parameters.

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 concretely defines the resource — open questions plus zero-result searches from the last 30 days — which is far more informative than the opaque name 'wanted'. It implicitly distinguishes itself from search_traces by describing a curated feed rather than a query interface, though it never states the verb (list/return) explicitly.

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 clearly signals the intended follow-up action and routes the agent to reply_to_trace with kind=answer, and the reputation incentive clarifies why an agent would read this feed. It stops short of stating when to prefer this over search_traces or how often to consult it.

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