scan_client_side_vulnerabilities

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

With zero annotations, the description carries full behavioral burden, but it only lists vulnerabilities covered. It doesn't disclose whether it requires authenticated sessions, whether it executes JavaScript in a browser, impact on web pages (destructive? intrusive?), or rate limiting. The reader knows what is scanned but not how the scan behaves.

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?

Three short lines, readable and front-loaded with the purpose. However, the bullet list adds value but the description is too sparse overall – not every sentence earns its place because there aren't enough sentences to cover the tool's needs.

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 focus (client-side vulnerabilities in depth), the complexity is non-trivial, but no output schema exists, no auth hints, no scope of scan (single page vs full site?). The description is incomplete for an agent to confidently invoke this tool 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 description coverage is 0%, so the description must compensate but only implies that target_url is the web server to scan. No format expectations (must include protocol? trailing slash?), no guidance on URL types supported. The single required parameter is under-documented.

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 the specific verb 'scan' and the resource 'client-side vulnerabilities', listing concrete vulnerability types (XSS, DOM XSS, Prototype pollution). This clearly distinguishes it from siblings like 'scan_website_comprehensive' which is broader, or 'scan_injection_attacks' which is server-side. A 5 would require explicit differentiation text.

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 guidance on when to use this vs alternatives like 'scan_website_comprehensive' (which might also cover client-side issues) or 'validate_xss' (a confirmed finding). No prerequisites, preconditions, or when-not-to-use advice provided. The agent must infer from context.

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