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

Annotations already mark readOnly and openWorld, and the description enriches them by explaining that all checks run via GitHub API (external network call), the rate limit (50 calls/IP/day), and the detailed output structure (letter grade, per-category scores, checks with evidence, prioritized recommendations). It does not contradict annotations.

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 two sentences with zero fluff. The first sentence leads with the core purpose and packs in the scoring range, categories, and outputs. The second sentence adds operational details (API-based, no clone, free tier). Every clause carries useful information.

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 an output schema present, the description doesn't need to elaborate on return fields. It covers the essential additional operational context: the 8 categories, security source (OpenSSF Scorecard), API-only execution (no clone), and rate limit. This is enough for an agent to decide when to invoke the tool and what to expect.

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 input schema already fully covers the single 'repo' parameter with a pattern and example, achieving 100% schema description coverage. The description adds general context about GitHub repos but no parameter-specific detail, so the baseline of 3 is appropriate.

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 opens with 'Comprehensive GitHub repository health audit', using a specific verb and resource. It enumerates 8 categories and output artifacts, making it unmistakable. Sibling tools are entirely different domains (revenue, token strategy, etc.), so it is clearly differentiated.

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 provides clear context: it audits GitHub repos, runs all checks via API, requires no clone, and offers free calls with a rate limit. It doesn't explicitly state when not to use it or name alternatives, but given the sibling contexts, the use case is unambiguous.

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