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

With no annotations, the description carries the behavioral burden. It discloses the call cost, implies a read-only 'snapshot' operation, and lists exactly what data is returned. However, it doesn't state auth needs, rate limits, error behavior, or confirmation that no repository is modified.

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?

Two sentences with no filler: the price is upfront, the returned fields are listed compactly, and the usage case is appended. Every phrase earns its place.

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?

The output fields are enumerated, which helps since there is no output schema, but the tool's sole input is opaque. Without an example or an explicit repo-identifier format, an agent cannot reliably construct a valid call, making the definition incomplete for invocation.

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 only parameter q has a generic schema description ('JSON or key=value input for the tool') and the top-level description never explains how to identify the repo (owner/name, URL, etc.). Even though schema coverage is 100%, the description adds no real parameter semantics, leaving the agent to guess the input format.

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 the resource ('GitHub repo') and enumerates the exact snapshot fields (stars, forks, open-issue count, watchers, primary language, SPDX license, dates, latest release tag), making the purpose concrete. It does not explicitly distinguish itself from the sibling repo_diligence, so it falls just short of full differentiation.

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 gives an explicit use context: 'Use to triage a repo before contributing or depending on it.' This tells an agent when the tool is appropriate, but it offers no exclusions or alternatives such as repo_diligence, so it doesn't reach the top score.

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