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

Annotations already cover read-only, idempotent, open-world, and non-destructive traits. The description adds valuable non-annotation behavioral context: 'Paid per call' and the explicit scope 'Public GitHub repository'. 'Read-only, no local context' restates annotations but reinforces them; no contradictions exist.

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 compact and front-loaded: the purpose and key data fields come first, followed by two short trait sentences. Every sentence earns its place; there is no fluff or repetition of the schema.

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 a single well-documented parameter and rich annotations, the description covers purpose, scope, safety profile, and cost. Although there is no output schema, the enumerated fields (stars, archived/maintenance status, license, last push, open issues/PRs, topics) effectively communicate expected return content. Nothing critical 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 description coverage is 100% — the 'repo' parameter is fully documented in the schema with format and example (owner/name, e.g. anomalyco/opencode). The description adds no further parameter-level detail, so the baseline 3 applies.

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 verb and resource: 'Public GitHub repository health check', and enumerates the exact data points returned (stars, archived/maintenance status, license, last push, open issues/PRs, topics). This clearly distinguishes it from all sibling paid_* tools, none of which target GitHub repository health.

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?

The description gives clear context: it applies to public GitHub repos only, is read-only, and has no local context. It implies when to use it (when you need public repo health data) and implicitly warns not to use it for local repositories, though it does not explicitly name alternative tools or exclusions.

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