rapid7_search

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

No annotations are provided, so the description carries the behavioral disclosure burden. It discloses an important behavior beyond simple keyword search: automatic extraction of MITRE TTPs, CVEs, and IOC markers. It does not detail result shape, pagination, or rate limits, but for a clearly read-oriented search tool this is a solid disclosure.

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 sentence with no wasted words. It front-loads the core action and source, then appends the valuable extraction behavior. Every phrase 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?

The description and fully documented schema cover the main purpose and parameters, but there is no output schema and no annotations. The description never explains the response structure or what the extracted fields look like, which is a meaningful gap for an agent trying to consume the results. It is adequate but not complete.

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 already documents both parameters, including the query semantics (keyword, CVE ID, or vulnerability name) and the limit's default and maximum. The description adds no new parameter-specific meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 states a specific verb ('Search'), a specific resource ('Rapid7 vulnerability research and threat intelligence blog'), and an additional behavior (extracting TTPs, CVEs, and IOC markers). This clearly distinguishes it from the many sibling source-specific search tools and makes its purpose unmistakable.

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 clear context that this tool is for searching Rapid7 blog content rather than other sources like NVD, CISA, or vendor advisories. It does not explicitly name alternatives or exclusion conditions, so it stops short of a perfect score, but an agent can reasonably infer when to use it.

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