Compare two public GitHub repositories side by side to assess repository health and identify differences in activity, issues, and maintenance signals.
Side-by-side health comparison of two public GitHub repositories.
| Name | Required | Description | Default |
|---|---|---|---|
| repo1 | Yes | ||
| repo2 | Yes | ||
| owner1 | Yes | ||
| owner2 | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full behavioral burden. It hints that only public repositories are accepted but says nothing about which health signals are compared, what happens with nonexistent or private repos, rate limits, or whether the two repos must be related.
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?
A single tight sentence with no filler and the key constraint ('two public repositories') front-loaded. Its brevity is efficient in form, though it borders on under-specification rather than padding.
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 described. But for a four-parameter comparison tool with zero annotation and zero schema-description coverage, the description omits comparison dimensions, error behavior, and parameter pairing semantics, leaving real gaps.
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%, with four required parameters documented only by bare titles like 'Owner1' and 'Repo1'. The description does not explain that the parameters form two owner/repo pairs, nor any format expectations (URL vs slug, case sensitivity), so it fails to compensate for the coverage gap.
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?
Names a specific verb ('health comparison') and resource ('two public GitHub repositories') in a single clear phrase. The word 'two' and 'side-by-side' implicitly separates it from the sibling repo_health, which handles a single repo, though that sibling is never named.
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?
No statement of when to pick this over repo_health, no prerequisites, no exclusions. An agent must infer that repo_health is the single-repo alternative and that private repositories are out of scope from the word 'public' alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.