sqlmap_scan

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

With no annotations, the description carries the full disclosure burden and mostly fails it. It hints at active exploitation ('exploits SQL injection vulnerabilities') and notes execution on a remote Kali machine, but says nothing about authorization requirements, typical runtime, or that dump/risk=3 can extract data or stress the target.

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 short sentences, front-loaded with the action and target, and free of filler. There is mild redundancy in restating 'SQL injection' twice (testing vs. detection/exploitation), which keeps it from a 5.

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 potentially destructive offensive-security tool with no annotations and no output schema, the description is too thin: it does not describe what results are returned, how long a scan typically takes, or any safety/authorization caveat. The rich parameter schema compensates partially, but the behavioral picture remains incomplete.

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 description coverage is 100%, so all six parameters (url, data, dbms, dump, risk, level) are already documented with examples and defaults in the schema. The description adds no parameter meaning beyond that, making the baseline 3 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 names a specific tool (sqlmap), a specific vulnerability class (SQL injection), and the target (a URL), which cleanly separates it from nmap_scan, gobuster_scan, and whatweb_fingerprint. It does not, however, explicitly contrast itself with the closest sibling, dast_scan, leaving that distinction to the agent's own knowledge.

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?

There is no when-to-use or when-not-to-use guidance: nothing says this should follow reconnaissance, that the URL must contain testable parameters, or when dast_scan/nikto would be the better choice. The agent must infer routing entirely from the tool name and the single sentence of purpose.

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