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

With readOnlyHint and openWorldHint already supplied, the description still adds substantive context: it reads lockfiles including transitive packages, has a 500-item ceiling requiring repeat calls, and defines the verdict domain with the critical warning that 'unknown' must never be reported as safe. That last point materially changes how an agent would interpret and relay 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?

Five short sentences, front-loaded with the trigger questions and scope, followed by operational limits and the verdict semantics. No filler or repetition; each sentence carries a distinct fact.

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?

No output schema exists, yet the description explains the verdict values and how to interpret 'unknown', which is the one return detail an agent must not misreport. Scope limits, input source, and batch ceiling are all covered, so nothing essential for correct invocation 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?

Given a single required parameter and reported 0% schema description coverage, the description compensates by specifying that versions must be exact installed versions (not ranges) sourced from lockfiles and that the list is capped at 500. It does not restate the ecosystem enum values, but the key semantic constraint on the array is conveyed.

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 concrete verb and resource: it checks exact installed package versions against public security advisories, and clarifies the input is a list read from the project's lockfiles. It implicitly separates itself from the singular sibling check_package via 'a list of exact installed package versions', but never names or references the sibling explicitly.

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?

Opens with the exact user questions it answers ('is my stack secure?', 'do we have vulnerable packages?') and closes with explicit exclusions: language runtimes, OS packages, Docker base images are out of scope. It also gives the operational boundary (up to 500 per call, call again for more), leaving little to infer.

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