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

No annotations exist, so the description carries the burden, and it delivers real behavioral context: supported Lucene syntax, the vendor/product field trap, and the fact that 'affectedSoftware' does not exist. It stops short of disclosing auth requirements, rate limits, or default result behavior beyond what the schema already states.

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 tool's role and the alternative-tool routing before the field caveat, and every sentence carries actionable content. Heavy emoji/ALL-CAPS emphasis and partial duplication of the schema's query description cost it a point.

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?

For a search tool with no output schema, it covers selection, alternatives, syntax, and field naming, and the fields parameter description conveys the default per-hit projection. Only the shape of the returned hits and pagination semantics are left implicit.

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 all four parameters (query, size, skip, fields) are already documented in the schema, including the 100 hard cap and the curated default projection. The description's query-field guidance largely duplicates the schema's query description, adding little beyond it.

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 ('Full-text search in Vulners Knowledge Base using Lucene syntax') and immediately frames itself as the discovery tool for unknown vulnerabilities. It explicitly distinguishes itself from sibling tools bulletin_by_id and audit_software by naming the cases each handles.

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?

Gives explicit when-to-use ('ONLY when you don't have specific IDs or version information') and two when-not-to-use rules, each routing the agent to the correct sibling (bulletin_by_id, audit_software). The vendor/product field requirement further constrains correct invocation.

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