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

Beyond the readOnly/openWorld annotations, it discloses that lookups consume credits and that "Repeated requests may purchase data again" (no caching), plus that built-by users only appear "when GitHub shows them." However, the cost statements conflict internally ("at least 10 Nexscope credits" versus "1 credit per request"), so the agent cannot actually predict spend from this text.

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 first three sentences are tight and front-loaded, but the tail is vendor boilerplate: "GitHub Trending Repositories API View Pricing Get GitHub trending repositories" is navigation scrap, and the filter list and price are restated two or three times with inconsistent numbers.

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?

For a no-required-param read tool with a 100% documented schema and no output schema, the description covers what is returned and what it costs, which is most of what an agent needs. The unresolved credit contradiction and the silent omission of result-count/pagination limits keep it from being complete.

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 the enum and examples are already documented; the description's only real addition is disambiguating coding language from spoken_language_code and hinting at permissive casing ("JavaScript or Python"). That is a genuine but small increment, matching the baseline 3 for a fully specified schema.

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?

"Scrapes GitHub's public Trending repositories page" gives a specific verb and resource, and the return-shape sentence (ranked repos, URLs, descriptions, language, stars/forks, built-by users) confirms what kind of data comes back. It never names the closest sibling, social_github_trending_developers, so the agent must infer the repositories-vs-developers split from the tool name alone.

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 tells the agent which filter to use for each concept (language vs. since vs. spoken_language_code), which is practical calling guidance. It gives no when-to-use or when-not-to-use guidance relative to the other GitHub tools (repository, user, trending_developers), leaving that routing to the name.

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