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

Annotations already cover read-only/open-world, so the description earns credit for adding the credit cost ('Costs 1 credit') and for decoding the result fields (likeCount, shareCount, starsInPeriod) that the agent cannot see anywhere else. It stops short of noting caching behavior despite exposing a cache_max_age parameter.

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?

Four short sentences, front-loaded with the resource and source, then the field decoding, then the cost. Every sentence carries information the agent cannot get from structured fields.

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 output schema, the inline field definitions are exactly the right compensation, and the credit cost is disclosed. The remaining gap is the undocumented cache_max_age parameter and no hint about result volume or caching semantics.

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?

At 50% schema coverage the baseline is 3; the phrase 'stars gained in the chosen period' usefully ties the `since` enum to the starsInPeriod field. But `cache_max_age` is left undocumented in both schema and description, and no slug/format guidance is added for `language` beyond what the schema says.

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 resource (trending repositories) and names the exact upstream source (the public github.com/trending board), which is more than a restatement of the name. The distinction from the sibling github_trendingDevelopers is only implicit in the word 'repositories', not called out.

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 implies the use case (browsing what's trending on GitHub) and that results are period-scoped, but it never says when to pick this over github_trendingDevelopers or github_activity, and gives no exclusions or prerequisites.

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