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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond the annotations: the score range (0-10), the list of per-check results, and supplementary metadata like stars, forks, and license. It explains what the tool evaluates, which informs expected behavior even though it doesn't discuss rate limits or auth.

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 front-loaded with the core purpose and then expands into output details and usage guidance. The phrase 'THE trust check.' adds emphasis but is slightly stylistic, and the projectile list of checks is dense though relevant. Overall it's well-structured and each sentence adds value, with only minor flourish preventing 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?

For a single-parameter tool with a rich output schema and safety annotations, the description covers everything an agent needs: what the tool returns, how to interpret the score, when to use it, how to obtain the required parameter, a concrete example, and the relationship to get_package_version. No critical guidance 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%, so the schema already fully documents projectKey, its required format, supported hosts, and how to obtain it. The description repeats this guidance with the same example ('github.com/facebook/react') and the get_package_version dependency, adding no new semantic information beyond the schema. Baseline 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 names a specific verb ('Get'), resource ('a project's OpenSSF Scorecard security posture and maintenance signals'), and enumerates concrete outputs. It distinguishes this tool from CVE-only lookups ('not just whether it has a known CVE') and positions it as the canonical trust check, clearly differentiating it from siblings like get_advisory.

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?

It explicitly says to use it 'to judge whether a dependency is actively maintained and securely operated' and clarifies that it is not merely a CVE check, implicitly steering away from get_advisory. It also gives a procedural prerequisite: obtain projectKey from a version's SOURCE_REPO link by calling get_package_version first. It doesn't name alternative tools for each when-not case, but the guidance is clear enough.

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