get_cve_details

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

No annotations are provided, so the description must fully disclose behavior. It mentions the tool retrieves details but does not confirm it is a read-only operation, specify any authentication needs, rate limits, or describe the response structure. This is insufficient for a tool with no annotation safety net.

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 a single, front-loaded sentence that conveys the essential purpose and return content without any unnecessary words. It is highly efficient for a simple tool.

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?

Given the tool's simplicity (one required parameter, no output schema), the description covers the core functionality and expected results. However, it lacks usage guidance and behavioral details, which slightly limits completeness for an agent unfamiliar with the context.

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?

The input schema covers the single parameter 'cve_id' with a regex pattern and description. The tool description adds semantic value by listing the types of details returned (description, CVSS score, severity, reference links), which enriches the agent's understanding of the output beyond the schema alone.

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 retrieves detailed vulnerability information by CVE ID, including description, CVSS score, severity, and reference links. This specific verb-resource combination ('get' + 'cve_details') and the explicit listing of return fields distinguish it from the sibling 'search_cves' tool.

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 implies usage via the input requirement ('根据CVE ID'), but does not explicitly state when to use this tool versus the sibling 'search_cves', nor does it provide any exclusions or prerequisites. Guidance is only implied.

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