Check Repo Health

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

With no annotations, the description carries the full burden. It discloses key behavioral traits: free, unauthenticated, uses GitHub's public REST API, enforces a 60 requests/hour/IP rate limit, and is read-only in nature. It does not explicitly cover failure modes (e.g., rate-limit exceeded, repo not found), but the most important operational constraints are clearly stated.

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 description is dense but not bloated. It front-loads the core purpose in the first sentence and packs usage, pricing, and API limits into the second. Every clause adds value, though it is slightly long and could be tightened without losing substance.

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?

Given no output schema, the description enumerates the return components (score, verdict, reasoning) and the scoring dimensions. It covers use case, rate limits, free/unauthenticated nature, and the paid alternative, making it a complete and self-contained description for an agent to decide when and how to use it.

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?

The input schema already provides 100% descriptive coverage for both parameters (owner and repo), so the baseline is 3. The description adds no extra parameter-level detail, but it does not need to; the schema examples are sufficient.

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 action ('Compute a maintenance/abandonment health verdict') on a clear resource ('a public GitHub repo') and details the output (0-100 score, verdict, reasoning). It fully satisfies the verb+resource+scope test and even differentiates itself from the paid API twin.

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?

It explicitly says 'Useful before depending on a library/tool' and contrasts with the paid alternative: 'for higher-volume or agent-automated x402-metered use, call the paid Worker endpoint instead.' It also mentions the rate limit (60 requests/hour/IP) as a constraint, offering clear context on when to use this tool.

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