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

Beyond the readOnly/idempotent/destructive annotations, the description adds valuable behavioral detail: the call is free and anonymous, one call covers the whole tree, and results fail closed with unverified entries so that an empty malicious list alone is not an all-clear. It also warns about the exact-version limitation, which is essential for interpreting results.

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 concise yet dense, with each sentence serving a purpose: what it checks, what it accepts, the exact-version limitation, and the fail-closed result interpretation. The key information is front-loaded, and there is no filler or redundancy.

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 read-only tool with an output schema, the description provides all necessary context: input format, limitation, service characteristics, and how to interpret results. Any remaining return-value details are covered by the output schema, so nothing critical 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?

The single parameter has 100% schema description coverage, so the baseline is 3. The description adds meaningful semantics about accepted lockfile formats and the exact-version requirement that tells an agent what kind of content is expected and what its limitations are, going slightly beyond the schema's purely syntactic description.

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 ('Check') and resource ('every EXACTLY-PINNED dependency in a lockfile') against published advisories, and specifies the accepted lockfile formats. It clearly distinguishes the tool from artifact scanning or attestation siblings by focusing on lockfile contents and malware advisories.

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 operational constraints: only exact-pinned versions can be answered, and range specs are not definitive. It also explains the fail-closed interpretation of the results. However, it does not explicitly name sibling tools or state when to choose one over another, so the routing guidance is implied rather than fully explicit.

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