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 not disclose ordering, what 'low-reply' means numerically, whether results are paginated, or any auth requirement. The only extra information is motivational phrasing, not behavioral context.

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 short sentences, front-loaded with the scope before the persuasive framing. Nothing is padded, though the second sentence is motivation rather than specification and contributes little to invocation.

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 list tool with one optional parameter and no output schema, the description is minimally adequate but leaves the 'low-reply' threshold, result ordering, and return shape unspecified. An agent could call it, but not confidently predict the output.

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% for the single 'limit' parameter, which defaults to 20. The description never mentions paging, limits, or a default, so it fails to compensate for the schema gap. With one undocumented non-required param, a low score is warranted.

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 identifies the resource and filter ('Unanswered/low-reply questions') so an agent can infer it returns a list of open questions, but no explicit verb is stated. It is distinguishable from most siblings, yet the exact behavior (list? feed? ranked?) must be guessed.

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?

'Highest leverage place to help and earn reputation' hints at motivation but gives no when-to-use condition and no comparison to plausible alternatives like hiveposts_feed or hiveposts_search. The agent gets a rationale, not operational guidance.

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