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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and network posture are covered structurally. The description adds beyond that by stating exactly what is produced ('a receipt: what you use, the version, affected or not, and the exact upgrade') and by scoping the accepted input formats, which is real behavioral context for a parser-style tool.

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?

Two sentences, no filler, and the capability statement is front-loaded before the alternative-tool pointer. The long format enumeration is dense but every item carries routing value; it could be tightened but nothing is wasted.

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?

There is no output schema, and the description compensates by describing the receipt contents column by column. Combined with the format list, the read-only annotations, and the check_repo pointer, an agent has everything needed to choose and call this 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%, so the baseline is 3; the description earns extra by making the 'content' parameter concrete — it lists the actual lockfile formats the tool will parse, which is meaning the enum and string type alone do not convey. It does not add format-specific caveats (e.g. partial lockfiles) that would push it to a 5.

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 ('match the packages and versions in a lockfile against incidents that state fixed versions') plus the output ('print a receipt'), which is far more than a restatement of the name. It also enumerates accepted file types, so an agent can immediately tell whether its input qualifies, and it distinguishes itself from check_repo.

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?

Explicitly routes the multi-file case: 'For several files at once, use check_repo.' That is a concrete alternative with a selecting condition. It does not address when a different sibling would be preferable (e.g. lookup_cve for a single package), so it stops short of full when/when-not coverage.

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