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

Annotations already declare read-only, idempotent and open-world behavior, yet the description adds genuinely new traits: counts are deterministic over every tracked release with no model judgment, the call caps at 100 packages, and untracked Maven/Go/NuGet packages are checked against deps.dev afterwards with per-day counting that records nothing about the caller. That last detail matters for privacy-sensitive agents. It stops short of 5 because latency, rate limits and what a miss does to the answer are not described.

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 block of roughly 200 words with long parenthetical enumerations (six package managers, three field mappings) that must be parsed before the tool's purpose emerges. Nearly every clause carries information, but the ordering is wrong for an agent skimming for 'should I call this?' and the single-paragraph form makes the toWanted/toLatest distinction easy to miss.

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 an output schema, full annotations and 100% param coverage, the description's remaining job is routing and behavior, which it does: ecosystem inputs, purl/repository fallbacks, the sibling handoff to upgrade_notes, and the deps.dev miss path. Nothing an agent needs to invoke it correctly is missing, though the response shape itself is left entirely to the output schema.

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 baseline is 3, but the description adds real meaning: it maps each ecosystem's CLI output onto the fields (npm outdated current→from, wanted, latest; pip version→from, latest_version→latest; go Version→from, Update.Version→latest), which tells an agent where to source values, not just what a field is. It also clarifies precedence (purl over name and registry) and the from-is-a-version-not-a-range rule, going beyond the schema's field-level text.

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 states a specific outcome: it returns per-package security releases, CVE ids and fixes the project lacks, split into toWanted (reachable in-range) and toLatest (needs a manifest edit), plus migration cost. That is far more than a restatement of the name and clearly separates it from upgrade_notes, which is called out as the tool for vendor breaking-change text. It loses a point only because this core statement is buried mid-paragraph behind input-format guidance rather than front-loaded.

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?

Usage is explicit and actionable: pass repository for scoped or renamed packages, use purl for Maven/Go/NuGet, call upgrade_notes for migration sections, set recordMisses: false for private packages, and split projects over 100 packages. There is no explicit 'do not use this when…' exclusion, so it falls short of a 5, but the alternatives and preconditions are named rather than inferred.

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