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 disclose the ranking basis (stars gained this week), implying a read-only ranked list, but says nothing about refresh cadence, stability of the ranking, paging, or whether results are deduplicated.

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?

One sentence, front-loaded with the resource and the metric, with zero filler. Nothing in it is redundant with the schema.

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 no annotations, no output schema, and 0% parameter description coverage, the description leaves too much unexplained for a two-parameter discovery tool: result shape, cap/default behavior, and the ecosystem filter's meaning and valid values are all unaddressed.

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%, so the description must compensate and does not: neither 'limit' (1-50, default 10) nor 'ecosystem' (enum of solana/base/robinhood-chain) is mentioned. The only clue is that the window is fixed at 'this week', which implies no time parameter exists.

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?

Specific: names the resource (repos in the index), the ranking metric (stars gained), and the time window (this week). It implicitly distinguishes itself from search_repos, but sibling differentiation is by inference rather than stated.

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?

No indication of when to use this versus search_repos or get_repo, no exclusions, no prerequisites. The agent is left to infer that this is the discovery/'what's hot' entry point from the description alone.

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