List Vulnerabilities (Action1)

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the tool is safe. The description adds minimal behavioral context (e.g., fetching one vs. listing). It doesn't disclose pagination, return format, or other traits. No contradictions with annotations.

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 consists of two concise sentences with no unnecessary words. It front-loads the core purpose and efficiently conveys key parameter semantics. 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?

With 10 parameters, no output schema, and limited description, the tool definition is adequate but not fully complete. The description covers core functionality and two parameters, but many aspects (pagination, filtering, sort) rely solely on schema comments. Annotations provide safety context, but overall completeness is moderate.

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 50%, and the description adds meaning for two parameters (cveId, detail). This improves understanding but leaves 8 parameters largely unexplained. Given the baseline of 3 for moderate coverage, the description's added value is adequate but not exceptional.

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 'CVEs across endpoints with score and remediation status,' specifying the verb (list/resource) and key attributes. It also explains parameter usage for fetching one CVE with cveId and listing endpoints or remediations with detail. This distinguishes it from sibling tools like list_endpoints or list_organizations.

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 provides context by explaining when to use cveId (fetch one) and detail (endpoints/remediations). However, it lacks explicit guidance on when to choose this tool over alternatives or when not to use it. Given no sibling tool lists CVEs, the usage is implicitly clear, but explicit exclusions would improve it.

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