wafw00f

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

With no annotations, the description carries full burden. It fails to disclose any behavioral traits such as network scanning behavior, rate limits, output format, or whether it requires specific privileges. The single phrase offers no behavioral context.

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. It could benefit from a brief sentence or bullet points. It earns a 3 for not being verbose, but it lacks substantive structure.

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?

Given the complexity of a WAF detection tool, the description is severely incomplete. There is no indication of what the tool outputs (e.g., WAF name, version), how to interpret results, or any dependencies. The presence of similar sibling tools (whatweb, wfuzz) without differentiation makes this inadequate.

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 only 33% (dry_run has a description). The description adds no meaning to the 'url' and 'session_id' parameters. The purpose of 'session_id' is ambiguous (e.g., session token or scan session), and no clarification is provided.

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 'Web Application Firewall detection' clearly states the tool's purpose: detecting WAFs. The verb 'detection' and resource 'WAF' are specific, and it distinguishes from siblings like ping or init_session, though it's somewhat similar to whatweb.

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?

No usage guidance is provided. The description does not indicate when to use wafw00f versus alternatives like whatweb or nikto, nor does it mention any prerequisites or conditions.

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