search_vulnerabilities

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

No annotations are provided, so the description must carry the full burden. It discloses that the tool returns collections and explains ordering behavior. However, it does not mention authentication (though api_key param suggests it), rate limits, or any potential side effects. For a search tool, this is adequate but not exhaustive.

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 well-structured with clear sections. The first sentence immediately states the purpose. It is concise without unnecessary words, and every sentence adds value (purpose, relation to other tools, parameter details).

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 presence of an output schema (though not detailed in the provided text), the description adequately explains the return type (list of collections). It covers ordering, limits, and the relationship to get_collection_report. It does not cover pagination or error handling, but for a search tool this is reasonable.

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 description adds significant meaning beyond the input schema, which lacks descriptions. It explains the query parameter's role, the default and possible values for limit and order_by, and the format of order_by ('+' for ascending, '-' for descending). The api_key parameter is not mentioned in the description, slightly reducing coverage, but overall it compensates well for the schema's lack of detail.

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 that the tool searches for vulnerabilities (CVEs) in the Google Threat Intelligence platform. It specifies the resource (vulnerabilities) and action (search), and distinguishes from siblings like search_threats by focusing on CVEs and mentioning how results can be used with get_collection_report.

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 on when to use the tool (searching vulnerabilities) and how to use the results (with get_collection_report). It also explains default ordering. However, it does not explicitly state when not to use it or compare with alternatives, but given the specificity, it is clear enough.

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