exploit_db_search

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

With no annotations, the description carries the full behavioral burden. It usefully reveals that results are recent submissions and that the tool automatically extracts TTPs, CVEs, and IOC markers. However, it does not disclose output structure, time-window semantics, pagination, or any access limitations.

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?

Two tight sentences, with the core action and resource in the first sentence and the value-added extraction behavior in the second. No filler or repetition of schema fields.

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?

The tool is simple, with two fully documented parameters, so the core call is understandable. However, without an output schema, the description only partially explains what the agent will receive, and it lacks any usage-or-alternative context amid the large sibling set.

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 coverage is 100%, so query and limit are already documented. The description restates that queries can be keywords or CVEs and adds the 'recent submissions' nuance, but it does not add meaningful detail about limit behavior or query formatting beyond the schema.

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 names a specific resource (Exploit-DB), a specific action (search), and the input focus (keyword or CVE). It also adds extraction behavior (MITRE TTPs, CVEs, IOC markers) that sets expectations beyond a simple search. This clearly differentiates it from sibling threat-intel search tools by source and purpose.

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?

No guidance is given about when to choose this tool over the many sibling search tools such as nvd_cve_lookup, malpedia_search, or otx_search_actor. The description implies use when Exploit-DB data is desired, but it does not state exclusions, alternatives, or typical scenarios.

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