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

Annotations only declare readOnlyHint and openWorldHint; the description goes far beyond by disclosing data-availability rules (boards from 2026-11-01 list only reviewed repos; earlier archived days may include unreviewed items), null semantics for rank fields, and the caveat that GitHub's own ordering differs from the returned rank. It also explains exactly how derived metrics are computed (stars_gained as an increment between timestamps, stars_per_hour over actual window hours, avg_stars_per_day for legacy records) and what previous_rank compares against per board type.

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?

The core purpose is correctly front-loaded in the first sentence, but the remainder is a dense, unstructured block that mixes input semantics, output-field semantics, and edge cases in one paragraph. Since an output schema already exists, several sentences explaining return fields are longer than needed and would read better as a short list of caveats.

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?

With annotations, a 100% covered schema, and an output schema, the description covers the remaining burden well: board availability windows, ranking caveats, null cases, and metric derivations. The only material gap is guidance on choosing this tool over siblings such as search_repos or get_repo, which an agent must still infer.

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% and both enums are documented, so the schema already carries the parameter burden — baseline 3 applies. The description reinforces date/period meaning ('for one UTC day', board-specific behavior for 'new'), but the bulk of its extra detail concerns output fields (best_github_rank_that_day vs best_github_daily_rank, previous_board_at, stars_per_hour) rather than adding input-parameter meaning.

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 opening sentence names a specific verb and resource ('Get a HotRepo trending board'), states the exact scope (repositories on GitHub Trending or the new-repository board for one UTC day), the ranking basis (stars gained, or measured Stars/hour), and the payload (each with a one-line review). No sibling tool (get_repo, search_repos, get_topic, get_monthly_report) returns ranked daily boards, so the distinction is unambiguous without naming an alternative.

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 scope statement rather than stated: an agent can infer this is the tool for 'what is trending on day X / in language Y', and the period semantics (daily/weekly/monthly/new) are explained. But there is no explicit when-to-use or when-not-to-use guidance, and no routing to search_repos or get_repo for non-board lookups.

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