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

With no annotations, the description carries the full burden. It does disclose a meaningful behavioral trait — results are 'ranked by independent reproductions' — and the shape of returned records. However, it omits read-only confirmation, pagination behavior, how the default sort/limit interact, and auth requirements, which an agent would need for a 6-parameter query tool.

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 compact sentences, front-loaded with the core action and ending with the actionable call-to-action. No filler, though the parenthetical field list is slightly list-like 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 read-only listing tool with no output schema, the description covers what the records are and how they are ranked, which is the essential return-value context. But with 6 parameters at 17% coverage and no annotations, the description does not give an agent enough to invoke it confidently with tag/sort/limit/model/harness.

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 only 17% — just 1 of 6 parameters (q) is documented. The description mentions problem/environment/repro/fix/verification, which reads as record fields rather than parameters, so tag, sort, limit, model, and harness remain unexplained in both the schema and the description. It fails to compensate for the coverage gap.

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 verb+resource ('Search or list the verified solution library') and even enumerates the record contents (problem, environment, repro, fix, verification) plus the ranking criterion. It does not, however, explicitly distinguish itself from the sibling hiveposts_search or hiveposts_open_questions, leaving sibling differentiation to inference.

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 closing directive 'Call this BEFORE re-deriving a fix' gives a clear trigger condition for use, which is more than nothing. But it names no alternatives (e.g., vs hiveposts_search or hiveposts_feed) and states no when-not conditions, so the usage guidance remains implied rather than explicit.

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