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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds real substance beyond that: live exploitation signal via CISA KEV, likelihood via EPSS, abandoned/deprecated detection, and a ranked fix-first ordering of results. It still doesn't mention auth, rate limits, or freshness of the vulnerability data.

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?

Three sentences, front-loaded with the core question and followed by what is checked and what is returned. No filler; each clause carries distinct information.

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 present, return values need no explanation, and annotations cover the safety profile. The description supplies the remaining needed context: input flexibility, the prioritization model, and the exploitation signals used.

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%, so the schema already documents manifest, packages, and ecosystem, including the name@version string form and the default npm ecosystem. The description's mention of a package list or pasted manifest only restates the schema, adding no format or precedence details. Baseline 3 applies.

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 opening line states the exact question the tool answers ('is my project safe?') and the resource it operates on (a package stack), then enumerates the concrete checks performed. This clearly separates it from brief_company, brief_domain, and brief_place, which cover entirely different resources.

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?

It signals the use case ('One call answers...') and states both accepted inputs (a package list or a pasted package.json / requirements.txt), which tells an agent when this tool fits. It stops short of naming when NOT to use it or pointing at the koot_watch/koot_unwatch siblings for ongoing monitoring.

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