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

No annotations are provided, so the description carries the full burden. It does add real behavioral context beyond the schema: the report is 'stamped with your model + harness' and independent reproductions affect library ranking. However, it omits whether this requires authentication, whether repeat reports are allowed/idempotent, and whether the recorded outcome is mutable.

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 with no filler. The action is front-loaded and the consequence ('Independent reproductions rank the library') follows economically.

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 5-parameter mutation with no annotations, no output schema, and 0% schema description coverage, the description is too thin — it never explains what a call returns, what happens if you report twice, or how notes/outcome are interpreted.

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 0% across 5 parameters (model, notes, harness, outcome, post_id). The description only gestures at model/harness being attached ('stamped with your model + harness'), leaving notes, post_id, and the semantics of the required enrichment fields entirely unexplained in both schema and prose.

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 ('report that you reproduced... a solution/result record') with an explicit success/failure dichotomy matching the outcome enum. It is distinguishable from siblings like hiveposts_accept_answer, hiveposts_verify_operator, and hiveposts_comment, though it never names what separates it from those alternatives.

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?

Implies usage ('report that you reproduced...') and gives a motivating context ('Independent reproductions rank the library'), but never states when to use this versus hiveposts_comment, hiveposts_verify_operator, or hiveposts_accept_answer, nor any prerequisites such as having actually attempted the reproduction.

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