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

Goes well beyond the readOnlyHint/idempotentHint annotations by disclosing the data provenance (daily-collected observatory data), the absence of quality scores, and a concrete data-quality caveat: delayed npm/PyPI reporting yields null days with notes rather than fabricated zeros. That caveat directly affects how an agent should interpret results and is exactly the kind of behavior structured fields cannot express.

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?

Front-loads the core action and metric definitions, then caveats, then routing advice — a sensible order with little waste. It is dense and semicolon-heavy, packing several claims per sentence, but no sentence is redundant.

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 an output schema present, return-shape explanation is unnecessary, and the description covers the remaining gaps: metric semantics, paging, data-quality caveats, and the sibling alternative. An agent has everything needed to invoke it correctly and interpret the numbers.

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%, so the description must carry the load — and it largely does: it names the two `metric_id` values with their meaning, explains `limit`/`offset` as paging over the full ranked list, and frames the 7d timeframe. It does not clarify what the `window` parameter accepts beyond 7d, leaving an ambiguity about whether other windows are valid.

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 (rank tracked entities by a project-level metric) and enumerates the exact entities and the two supported metrics with definitions. It also explicitly distinguishes itself from the sibling `get_github_trending`, so an agent can pick the right tool without opening the schema.

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?

Gives an explicit trigger ("Use when the user asks what is rising") and an explicit alternative for the adjacent case (the daily GitHub Trending list → `get_github_trending`). Both when-to-use and when-to-use-something-else are covered.

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