sqlmap

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

No annotations are provided, so the description carries the burden. It discloses that the tool is automated, handles detection/fingerprinting/dumping/shell access, and runs non-interactively by default (via opts default). However, it doesn't disclose potential side effects like network traffic, time delays, or the fact that exploitation can be intrusive/destructive. A 3 is fair: it adds useful behavioral context but omits risk-related behavior.

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 compact and front-loaded: it states the core function first, then usage context, then output, then alternatives. Every sentence earns its place; no filler or repetition.

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 tool with 2 params, 100% schema coverage, and no output schema, the description covers the main gaps: what it does, when to use it, what output to expect, and how it differs from siblings. It doesn't mention risk/intrusiveness, which is a minor gap for an exploitation tool, but overall it's complete enough for an agent to select and invoke it correctly.

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 the schema already documents both parameters. The description adds context about the default opts ('--batch --random-agent') and the output, but doesn't add much beyond the schema. Baseline 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 ('Automated SQL injection detection, exploitation, and data extraction') and names the resource (URL parameters). It also distinguishes itself from siblings by naming commix and xsser as alternatives for other vulnerability classes. This is a clear, specific purpose statement that an agent can act on.

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 explicitly says 'Use when you find a URL parameter that may be injectable' and provides exclusions: 'For command injection (not SQL), use commix. For XSS, use xsser.' This is exactly the kind of when-to-use and when-not-to-use guidance that helps an agent select the right tool.

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