wpscan_scan

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

With no annotations, the description carries the burden of disclosing behavioral traits. It mentions detection modes, throttling, random user agents, and TLS checks, which provide useful operational context. However, it does not disclose potential disruptive effects, authorization requirements, or how results are returned (e.g., synchronous vs. asynchronous), leaving significant gaps.

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 formatted as a structured bullet list, making parameters easy to scan. Each line is purposeful and compact, though the enumerate explanation is slightly verbose. Overall, it earns its place without excessive fluff.

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 thoroughly covers parameters but omits key operational details like output format, whether the scan is synchronous or asynchronous, and how to interpret results. Given the lack of an output schema and the complexity of a scanner, these missing pieces prevent full completeness.

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 has zero property descriptions, but the tool description explains every parameter: url, enumerate with value breakdown, api_token, detection_mode, random_user_agent, disable_tls_checks, and throttle_ms. This fully compensates for the absent schema descriptions and adds practical guidance such as the API token source and enumerate value meanings.

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 explicitly identifies the tool as a 'WordPress vulnerability scanner using WPScan', which is a specific verb+resource and clearly distinguishes it from generic scanners like nmap_vuln_scan or nikto_scan. The name and description align perfectly, leaving no ambiguity about the tool's function.

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 intended use case (scanning WordPress sites) is clearly implied by the purpose, but there is no explicit guidance on when to choose this tool over alternatives, nor any mention of exclusions or prerequisites. It does not reference sibling tools or state 'use when the target is WordPress'.

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