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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds meaningful behavioral context: it returns deprecation status and emphasizes the precision of CPE strings, which is not apparent from annotations or schema. It does not contradict the annotations, and adds value beyond them.

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?

The description is two sentences with no wasted words. The core purpose and return values are front-loaded, and the usage guidance is placed right after. It is concise, structured, and every sentence earns its place.

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 read-only search tool with annotations covering safety and an output schema, the description is complete. It covers what the tool does, what it returns, and when to use it. The only potential gap (pagination behavior) is already documented in the schema via the offset description. An agent has everything needed to call it correctly.

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 parameters (limit, offset, keyword, cpeMatchString) are already documented in the schema. The description reiterates the two main search modes (keyword or partial match) but does not add new meaning beyond the schema. Baseline 3 is appropriate since the schema handles parameter documentation.

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 clearly states the tool's purpose: searching the NVD CPE dictionary by keyword or partial match, and lists the return types (CPE names, titles, deprecation status). It explicitly differentiates itself from the sibling nvd_audit_cpe by explaining it is a prerequisite for that tool, so an agent can immediately tell when to use it.

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?

The description gives explicit guidance: 'Use before nvd_audit_cpe to resolve the correct CPE name'. It also explains why exact matching matters, which helps the agent understand the workflow. While it doesn't list exclusions for every sibling, the primary alternative is named and the usage context is clear.

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