scan_and_exploit_chain

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

With no annotations, the description carries the burden of behavioral disclosure. It explains that the tool returns matching exploits and service versions, which clarifies it is a lookup/search rather than an actual exploitation tool. However, it does not mention potential duration, impact of scanning, or that it does not execute exploits—additional context would improve transparency.

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 concise, front-loaded with the core idea, and uses a clear chain notation. Three sentences cover purpose, parameters, and return value without wasted words. Structure is easy to parse.

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 chained tool with two parameters and no output schema, the description covers purpose, parameter meanings, and return structure. It lacks notes on runtime expectations or safety considerations, but the provided information is sufficient for an agent to understand the tool's role and select it appropriately.

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?

Despite 0% schema description coverage, the description adds meaning by specifying 'target: IP or hostname' and 'ports: port range to scan'. This goes beyond the bare schema property names and clarifies expected input formats. It could be even more detailed (e.g., port syntax), but it adequately compensates for the schema gap.

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 the tool performs a full chain (port scan → service detection → CVE lookup) and returns exploits for each service. This distinguishes it from individual sibling tools like nmap_port_scan or searchsploit_search by emphasizing the combined action.

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?

It conveys the use case: get all exploits for all services in one call. It implies a holistic alternative to running separate scan steps, but does not explicitly mention when not to use it or name alternative tools for specific steps. The context is clear, but exclusions are absent.

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