websex_arjun

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

With no annotations, the description carries the full burden, and it does disclose meaningful execution semantics: argv tokens are passed directly, shell parsing is never used (no shell injection), and the process runs from the engagement namespace. It stops short of disclosing anything about network reach, runtime, or what the tool produces, so a 3 is warranted.

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 sentences, front-loaded with the action, no filler or repetition. It is tight, though it spends its budget on execution mechanics rather than the information an agent most needs (what the tool discovers).

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?

An output schema exists so return values need not be explained, but for a 4-parameter tool with 0% schema coverage the description leaves too much unsaid: no statement of what arjun discovers, no selection guidance against two close siblings, and no runtime or scope expectations.

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. It usefully clarifies the most important parameter by stating that 'arguments' is a raw argv token list rather than a shell string, and the relative-path note touches working_directory. However, stdin and engagement_id are left entirely undocumented.

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 only restates the tool name: 'Run arjun from the WebSex web toolkit.' It never says what arjun does (HTTP parameter discovery) or what it targets. With siblings websex_paramspider and websex_x8 covering the same domain, there is no differentiation at all, so an agent unfamiliar with the binary cannot pick it correctly.

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?

There is no when-to-use guidance and no mention of the obvious alternatives (paramspider, x8) that would let an agent choose. The only usage-like sentence concerns namespace and relative paths, which is an operating instruction rather than selection guidance.

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