bulk_cve_lookup

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

With no annotations, the description carries the full burden. It discloses concurrent execution, max 20 limit, and return format (dict with severity info). Lacks details on error handling or authorization, but provides solid behavioral context.

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?

Three concise sentences, each providing unique information: action, use case, return format. No redundancy or fluff. Front-loaded with the primary verb and resource.

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 tool with 1 parameter and no annotations, the description covers purpose, constraint, use case, and output structure. It lacks details on error handling for invalid IDs, but the output schema likely covers return structure. Adequate for the complexity.

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 has 0% description coverage, so description must compensate. It explains the parameter's purpose: 'Look up multiple CVEs by ID' and the use case. Adds value beyond the raw schema, though could more explicitly describe the array element format.

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?

Description clearly states the action (look up multiple CVEs), resource (by ID), and constraint (max 20 IDs). It also provides a specific use case (scanning dependency lists from pull requests), distinguishing it from sibling tools like search_cve_by_id.

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?

Description explicitly notes the tool is useful for scanning dependency lists from PRs, implying when to use. It also mentions the max 20 IDs constraint, which guides usage. However, it does not explicitly exclude alternatives or say when not to use.

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