generate_xss_callback

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

With no annotations provided, the description carries the full burden. It discloses that the tool creates JavaScript payloads that ping a webhook when executed, and that options exist for capturing DOM info and cookies. It does not cover all edge cases but is transparent about core behavior.

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 two sentences, front-loading the purpose and mechanism. Every sentence adds value without 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?

The description explains the purpose and behavior but omits the output format (e.g., what the payload looks like). Since there is no output schema, this information is missing. It also does not clarify how to use the generated payload in testing scenarios.

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 100%, so the baseline is 3. The description reiterates the parameters' purpose (e.g., webhook_token, identifier) but adds no new meaning beyond the schema's own descriptions. It does not suggest parameter interactions or constraints.

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 identifies the tool as generating XSS callback payloads for bug bounty testing, using a specific verb and resource. It distinguishes from siblings like generate_ssrf_payload and generate_canary_token by focusing on cross-site scripting.

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 states the tool is useful for detecting blind XSS, implying a use case. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., generate_ssrf_payload), nor does it mention when not to use it.

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