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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond repeating the scope dimension — nothing about pagination via cursor, sort semantics, or default date resolution, all of which materially affect calls.

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 with no filler; the scope enumeration is the most decision-relevant content and comes first. It is arguably too terse for a nine-parameter tool, but nothing is wasted.

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. However, with nine optional, interdependent parameters (day/month/year/week/date plus cursor and order), the description omits any guidance on how these combine or which to set, leaving a gap for a tool of this complexity.

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 100%, so all nine parameters are already documented in the schema (including scope values, defaults, and date/field interdependencies). The description's mention of scopes duplicates schema content and adds no syntax or default guidance beyond it, 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?

States a specific verb and resource ('Fetches Product Hunt leaderboard data') and enumerates the scope dimension (daily/weekly/monthly/yearly), so an agent knows it returns ranked Product Hunt data. It does not distinguish itself from siblings like producthunt_launches or producthunt_search, leaving the boundary implicit.

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 description says what the tool returns but never says when to choose it over producthunt_launches, producthunt_search, or producthunt_category_products, nor when to pick one scope over another. No prerequisites, no exclusions, no alternative routing.

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