Waf Vendors

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

The annotations already declare readOnlyHint and non-destructive behavior. The description adds a slight context by indicating it lists supported vendors and payload classes, but it does not elaborate on any potential side effects (though none exist). It is consistent with annotations, but adds minimal extra transparency.

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 a single, concise sentence with no unnecessary words. It efficiently communicates the tool's purpose without any fluff or redundancy.

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 tool's simplicity (no parameters, no complex behavior), the description is complete for an agent to understand what it does. An output schema exists, so the description need not explain return values. No additional context is required for this straightforward listing operation.

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 tool has no parameters and the schema coverage is 100% (empty schema fully covers the tool). Per the rubric, with high schema coverage, the baseline score is 3. The description does not need to explain parameters since there are none, and it does not add any parameter-related information.

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 clearly states the tool's function: 'List supported WAF vendors with the classes each has bypass payloads for.' It uses the specific verb 'List', identifies the resource (WAF vendors), and specifies the detail about bypass payload classes, distinguishing it from sibling tools like waf_bypass or fingerprint_waf.

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 gives no explicit guidance on when to use this tool versus alternatives. It does not mention, for example, that this is for reconnaissance/inventory and not for actual bypassing, which is covered by waf_bypass. No usage context is provided beyond the basic function.

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