What a community upvotes

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description usefully adds a cost model (budgetUsd held during the run then released) and an auth prerequisite ('Needs the write scope'), but it leaves the tension between a read-only tool and a write-scope requirement unexplained, which can mislead an agent about whether anything is mutated.

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 short sentences with the return content front-loaded, and the cost/scope caveats placed after. The staccato 'Free: ...' fragment is slightly awkward but nothing is wasteful or padded.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile; the description fills the remaining gaps (cost mechanics, credential scope). What is missing is routing guidance against sibling trending tools, which keeps it from a 5.

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 100%, so both parameters (budgetUsd default/max, community values) are already fully documented in the schema. The description repeats the budget default and max without adding syntax or format detail beyond the schema, so the baseline 3 applies.

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 names a specific resource and scope ('the live top of Hacker News or of a subreddit's hot ranking, with scores'), which is unique among siblings like x_pulse and news_search and lets an agent tell what it returns. The verb is only implicit (a fetch/list), and no sibling is named for contrast, so it falls short of a 5.

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?

Usage is implied by the domain ('what a community upvotes'), but there is no explicit when-to-use, when-not, or pointer to an alternative (e.g. x_pulse/current_pulse for other trend sources). The agent must infer that this is the tool for HN/subreddit rankings rather than being told.

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