validate_xss

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

No annotations are present, so the description carries the full burden. It does not disclose whether 'validate' is a read-only check or sends malicious payloads (which could be destructive). There is no mention of permissions, rate limits, or side effects, leaving the agent uncertain about the tool's impacts.

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 sentence but is under-specified. Conciseness should not come at the cost of essential information. The structure is not front-loaded with critical details like behavior, prerequisites, or parameter semantics.

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 has 3 parameters, no annotations, and no output schema, the description is highly incomplete. It omits what the tool returns, how to interpret results, the workflow for validation, and any dependencies. An agent would have insufficient information to use the tool effectively.

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%, meaning the schema itself provides no parameter descriptions. The tool description adds no meaning: it does not explain what 'target_url', 'parameter', or 'payload' represent, how they should be formatted, or what the optional payload defaults to (schema shows default null but no clarification).

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 'Validate XSS with proof of concept' uses a specific verb ('validate') and resource ('XSS'), and adds 'with proof of concept' to hint at execution. However, it lacks differentiation from sibling tools like 'validate_sql_injection' and 'scan_injection_attacks', leaving ambiguity about what validation specifically entails (e.g., checking for reflected or stored XSS).

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 provides no guidance on when to use this tool versus alternatives, nor any prerequisites or usage contexts. An agent would not know if this should be used after a scan, for specific payloads, or for verification of a discovered vulnerability.

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