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

Annotations already cover read-only/idempotent/open-world safety, and the description adds real operational context beyond them: a 10-minute in-process cache, stale-on-rate-limit fallback behavior with an ok:false signal, the upstream source (api.github.com, keyless), and the x402 pricing (0.03 USDC per call, first call free). These are exactly the traits an agent cannot derive from structured fields.

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 dense, front-loaded block: purpose first, then caching/error semantics, then source and pricing. Nothing is wasted, though cramming billing and cache policy into one sentence makes it slightly harder to scan.

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?

No output schema exists, so the description's field list (stars, forks, issues, push date, language, archived) carries the return-value burden and does so adequately. Combined with cache/error semantics, pricing, and the keyless source, an agent has everything needed to call it correctly.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already documents 'owner/repo'. The description restates the same format without adding syntax detail, validation rules, or examples beyond the schema — the baseline 3 for schema-covered params.

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 (public GitHub repo activity metrics) and enumerates exactly what is returned: stars, forks, open issues, last push, language, archived flag. No sibling tool covers GitHub, so it is unambiguously distinguishable.

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?

Gives the required input shape (owner/repo), states it works on any public repo and is keyless, which implies usage context. However it never states when to use this versus alternatives or when it is inappropriate (private repos, non-existent owners), leaving selection logic to inference.

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