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

Annotations already declare readOnlyHint/openWorldHint/idempotentHint and destructiveHint=false, so the description only needs to add behavioral value. It does so by listing the concrete Scorecard checks and additional repository signals returned, making the read-only trust-assessment behavior transparent.

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 with purpose, then delivers output details and usage guidance. The only marginally nonessential flourish is the sentence 'THE trust check,' but it does not meaningfully hurt clarity.

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 parameter, no output schema, and strong annotations, the description covers purpose, return contents (Scorecard overall and checks, stars, forks, open issues, license), and parameter sourcing. This gives an agent enough context to select and invoke the tool correctly.

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 coverage is 100%, and the schema description already documents the raw/unencoded format, supported hosts, and where to get the value. The tool description repeats the source and example without adding new semantic meaning, so the 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 opens with a specific verb + resource ('Get a project's OpenSSF Scorecard security posture') and then names the exact payload: overall score, per-check results, and repository stats. It also positions itself as 'THE trust check' and contrasts with CVE-only checks, distinguishing it from sibling get_advisory and get_package_version.

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 'Use it to judge whether a dependency is actively maintained and securely operated — not just whether it has a known CVE,' defining the decision context. It also gives the prerequisite workflow: call get_package_version first and take the projectKey from the version's SOURCE_REPO link.

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