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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. Beyond that the description discloses almost nothing behavioral: no mention of GitHub API rate limits, token/auth requirements, runtime cost, or what the 'AI assessment' actually returns or how it is derived.

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 visibly duplicated and truncated, presenting a short ellipsis-terminated sentence followed by a longer restatement of the same content. This redundancy and trailing ellipsis hurt structure and front-loading.

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?

For a read-only, open-world analysis tool with no output schema, the description should convey what the agent gets back, any auth or rate-limit constraints, and cost. It lists the metrics but omits all operational context needed to call it correctly and interpret results.

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?

There is a single parameter and schema description coverage is reported at 100%, so the baseline is 3. The description adds no meaning about the nested input object (e.g. what fields the repo identifier accepts), leaving that entirely to the 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?

The description names a specific verb and resource ('Analyze any GitHub repository's health') and enumerates the measured dimensions (stars, activity, release cadence, contributor concentration, issue responsiveness, license). It is clear what the tool produces, though it does nothing to distinguish itself from siblings like github_candidate_scorer or npm_package_intelligence.

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?

There is no statement of when to use this tool, when not to, or what alternative to prefer for adjacent needs such as scoring a candidate or vetting an npm package. The only usage cue is 'any GitHub repository', which restates the resource rather than guiding selection.

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