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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds two genuinely useful facts not in the schema: results come back one page at a time with a total, and only the first 10,000 matches of a filter are reachable. It says nothing about filter combination semantics (AND/OR) or what an unfiltered call returns.

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 short sentences, front-loaded with what the tool returns and followed by the one hard constraint. Nothing is redundant and nothing needs trimming.

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 15-parameter search tool with no output schema, the description covers the result envelope (page plus total) and the deep-paging cap, which are the highest-value omissions in the schema. It leaves out how the many filters combine and what happens with zero parameters, which an agent needs before composing a broad query.

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%, with per-parameter docs, enum explanations and examples, so the schema carries parameter meaning. The description only restates the default ordering ("newest first"), which the sort and dir parameters already document; baseline 3 is appropriate.

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?

"Finds CVEs matching a filter and returns one page of them" gives a specific verb (finds) and resource (CVEs) plus the shape of the result. It implicitly distinguishes itself from get_cve, which returns a single CVE, though it never names that sibling explicitly.

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?

There is no explicit when-to-use or when-not guidance and no routing to alternatives such as find_filter_values (to discover valid vendor/product values) or get_cve (to fetch one record). Usage must be inferred entirely from the name and the filter parameters.

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