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

Beyond the readOnly/idempotent annotations, it discloses real behavioral limits: coverage is only the current and previous quarter, results are newest-first, matching is subject-only so absence is not proof of no advisory, and the index refreshes weekly. These are exactly the caveats an agent needs to interpret an empty result correctly.

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?

Front-loaded with the trigger question, then parameters, then what returns, then the important caveats — a good ordering. It is slightly padded by repeating package examples (openssl, ffmpeg, tomcat) that already appear in the schema.

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?

Even though an output schema exists, the description summarizes the return shape (subject, link, CVE ids) and pairs it with the subject-only matching caveat and freshness cadence. Nothing needed to interpret results or avoid a false negative 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?

Schema coverage is 100% and the schema already documents examples and the anyOf constraint on package/cve, so the description's 'pass package ... or cve, not both' largely restates structured data. The only added nuance is framing the values as 'a name as advisories write it', which is marginal.

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 names a specific verb and resource (search oss-security mailing list threads) and frames it around the concrete user question it answers, complete with an example query. It is clearly separable from siblings like check_cve or list_recent_kev, which operate on different sources.

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 gives explicit trigger context ('when the user asks whether a security issue was announced...') and states the parameter choice rule: pass package or cve, not both. It never names an alternative tool such as check_cve for the structured lookups, so routing between this and siblings is only implied.

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