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

With no annotations, the description carries the full behavioral burden and does well: it discloses the scoring formula (1 point per vote, 0.5 per comment), a 90-day decay so recent demand outranks old, and tie-breaking to the newer request. It stops short of stating read-only-ness explicitly or whether results are paginated.

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?

A single front-loaded sentence that leads with what is returned and the exclusion rule, then explains ranking. Dense but every clause carries meaning; only slightly long.

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?

No output schema and no annotations, so the description must stand alone — and it explains what is returned and how ordering is computed. It omits the result shape/pagination and the limit parameter, which is a minor gap for a simple read tool.

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 coverage is 0% and the single parameter 'limit' is never mentioned in the description. 'Top requests' implies a bounded ranked list, but the default of 5 and maximum of 20 are left for the schema alone, so the description does not fully 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 and resource ('Get the top feature requests') plus the scope constraint ('excluding requests already marked done'), which separates it from the sibling list_requests. It does not name an alternative tool outright, but the ranking/exclusion scope makes the purpose unambiguous.

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 ranking semantics — call it when you want the highest-demand requests rather than an unfiltered list — but there is no explicit when-to-use statement or pointer to list_requests/get_request as alternatives. Adequate but leaves routing to inference.

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