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

Goes far beyond the readOnlyHint/openWorldHint annotations: it discloses the scoring formula and weights, tier thresholds, the one-API-call-per-repo cost, npm/PyPI lookups, partial-failure behavior (notFound vs total failure), rate-limit and token-rejection failure modes, and the 50-call/day hosted quota with the X-GitHub-Token escape hatch. This is unusually rich operational context.

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-loaded with the core comparison purpose and output, and every clause carries real information (weights, tiers, failure modes, quota). It is a dense single paragraph rather than a tautological one, though the sheer density slightly hurts scannability.

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 description still explains return values (score, tier, verdict, breakdown) and the notFound container, and it covers auth, rate limits, and failure conditions. Nothing an agent needs to call this correctly is missing.

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% and it already documents owner/repo format and the 2-10 range, so the baseline is 3. The description still adds value by emphasizing 'known' repositories (i.e. ones that must exist and can land in notFound) and repeating the 2-10 bound in context, reinforcing the constraint beyond the raw 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?

States a specific verb (compare) and resource (2-10 known GitHub repositories), plus the output shape (score, tier, stars, forks, verdict). It explicitly distinguishes itself from recommend_repos in the same sentence, so an agent can route between the two siblings without extra inference.

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?

Names the exact scenario ('choose between candidates you already have, for example zod vs valibot') and its alternative ('use recommend_repos to find candidates'). The when-to-use vs when-not distinction is explicit and actionable.

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