tools_sqlmap

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

No annotations are provided, so the description must disclose behavioral traits, but it says nothing about SQLMap's actions, potential impact, required permissions, or side effects. It does not mention that SQLMap sends HTTP requests, can perform invasive tests, or may require network access.

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 extremely short, but this is under-specification rather than conciseness. While it is front-loaded and has no wasted words, it omits essential information, making it ineffective.

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 9 parameters, no annotations, and no output schema, this description is thoroughly inadequate. It does not explain the tool's purpose, parameters, usage, or behavior, leaving the agent with no actionable context.

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 0%, and the description does not explain any of the 9 parameters. It fails to clarify the meaning, format, or relationships of parameters like url, dbs, dump, or additional_args, which are crucial for correct invocation.

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 'Execute SQLMap' is essentially a restatement of the tool name with a generic verb. It identifies the target tool (SQLMap) but provides no specifics about what SQLMap does or what the tool accomplishes. This is a tautology rather than a clear purpose statement.

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 guidance on when to use this tool or how it relates to alternatives like tools_ghauri or other scanners. The description merely says 'Execute SQLMap,' with no context on prerequisites, target selection, or expected scenarios.

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