xsser

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

With no annotations, the description carries the full behavioral burden and does disclose two useful traits: automatic payload encoding ('Automatically encodes payloads to bypass filters') and output shape ('identified XSS vectors with payload and injection point'). However, it is an 'exploitation framework' yet never discloses operational side effects — that it actively fires payloads at the target, request volume/noise, or authorization expectations — so an agent cannot gauge the impact of invocation.

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?

Four sentences, roughly 75 words, logically ordered: purpose first, then trigger condition, key behavior, sibling routing, and output. Every sentence earns its place and the most decision-critical info (what it is, when to use it) is front-loaded.

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?

For a two-parameter tool with no output schema, the description covers purpose, trigger, behavior, alternatives, and return format — most of what an agent needs to invoke it. The gap is risk context: an 'exploitation framework' with no annotations should flag that it actively sends attack payloads and is for authorized targets only. That omission is meaningful for offensive tooling.

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 both parameters are already documented, including a concrete URL example ('http://example.com/search?q=test') and the --auto default for opts. The description adds mild context for what the URL will be used for but no parameter-level syntax or format details beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'XSS detection and exploitation framework' and enumerates the exact coverage ('reflected, stored, and DOM-based XSS'). It distinguishes itself from sibling tools by routing other vulnerability classes elsewhere ('For SQL injection, use sqlmap'), so an agent can tell xsser apart from sqlmap, nuclei, and nikto without opening schemas.

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?

'Use when you find user input reflected in page output' is an explicit, actionable trigger condition. It also names concrete alternatives for adjacent tasks ('For general web vulnerability scanning, use nuclei or nikto. For SQL injection, use sqlmap.'), effectively providing the when/when-not guidance the rubric rewards.

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