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

Read-only is already covered by annotations, but the description adds genuinely useful behavioral context: the data source (own hourly snapshots), the fixed 24h window, the 'genuinely moved' noise-filtering guarantee, and the sign convention for 'positive climb = went up'. It does not state ordering of the returned list, which would have completed the picture.

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?

Two tight sentences that front-load the core definition and use the parenthetical to establish data provenance. No filler, though the second clause about the movers strip is more marketing than operational.

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 the 24h window and sign convention are covered. What is missing is anything about the board taxonomy (what 'rising' vs 'dark' vs 'overlooked' actually ranks) and the fact that limit caps the movers returned.

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 carry the parameter burden and does not. The slug enum lists ten values whose meaning is opaque without domain knowledge ('dark', 'overlooked', 'controversial', 'milestone'), and 'limit' (default 10, max 20) is never mentioned at all.

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 states a specific resource and scope: repositories that changed rank on a board within the last 24 hours, sourced from an hourly snapshot series. That distinguishes it in substance from get_board (full board snapshot) and get_repo_history (single repo over time), though it never names those siblings explicitly.

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?

There is no when-to-use instruction, no guidance on choosing among the ten board slugs, and no explicit alternative named (get_board is the obvious one for a static listing). Usage is only inferable from the 'on-site movers strip' analogy.

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