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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds the output range (0-10), which is genuinely useful context, but it omits an important behavior: all three parameters are optional in the schema, yet the tool is useless unless the caller supplies either package+ecosystem or github_repo.

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 front-loaded sentence that names the data source, the metric, and the accepted input types without padding. The trailing '(#1 in MCP Registry)' is marketing content that does not help an agent decide or call correctly and prevents a 5.

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 only three simple, fully documented parameters and no output schema, the tool's core is adequately covered. The gap is the missing input-selection rule (package+ecosystem vs github_repo), which is the one thing an agent could actually get wrong at call time.

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%, so each parameter is already documented with examples, and the description adds no syntax or pairing rules beyond that. The baseline of 3 applies; it would need to explain that 'package' pairs with 'ecosystem' while 'github_repo' is the alternative input path to score higher.

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 uses a specific verb ('Query') and names two concrete upstream sources (deps.dev and OpenSSF Scorecard) plus the accepted scope (GitHub repository or package). It does not distinguish itself from overlapping siblings like package_health_pulse or cyber_supply_chain_security_dossier, so it falls short of a 5.

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 prefer this tool over package_health_pulse, security_cve_audit, or the supply-chain dossier siblings, and no exclusions or prerequisites. The only implicit guidance is the phrase 'for any GitHub repository or package', which hints at scope but not routing.

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