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

Annotations already declare read-only and open-world behavior; the description adds non-obvious context the annotations do not: the OSV.dev data source, the 1,000-version cap, what is returned (affected packages, severity, upgrade versions), and critically the $0.05 USDC x402/prepaid pricing and exclusion from the free trial. That payment/auth constraint is exactly the kind of disclosure the annotations cannot convey.

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?

One dense capability sentence front-loads the verb, scope, formats and limits, with pricing isolated in a short follow-up sentence. Slightly overloaded with a nine-item format list, but nothing is padded.

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 audit tool with an output schema already covering return shape, the description supplies formats, version cap, data source, and payment terms. A minor gap remains on what happens when neither url nor content is supplied, and on rate limits/latency, but it is otherwise complete.

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% and all four params (url, format, content, filename) are self-documented in the schema, so the baseline is 3. The description adds only the 1,000-version ceiling and the 'use url for bigger files' hint, which is marginal over 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?

States a specific verb and resource ('Audit a whole lockfile') plus the exact scope envelope (whole lockfile, one call) that separates it from the sibling package-audit / package-check / package-upgrade tools. An agent can pick this over its siblings without opening either schema.

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 phrase 'a whole lockfile ... in one call' signals the use case versus per-package audit siblings, and the enumerated format list scopes applicability clearly. It stops short of an explicit 'use X instead when Y' routing statement, so it is strong context rather than full guidance.

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