websex_hashpump

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that argv tokens are passed directly and shell parsing is never used, and that execution occurs in the engagement namespace, which tells the agent about injection semantics and path resolution. However it says nothing about whether the operation is read-only, resource limits, or side effects.

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 tightly written sentences with the execution guarantee front-loaded and no filler. Nothing is repeated from the schema and every clause carries information.

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, and the execution model is covered. The remaining gap is substantive: the tool's actual analytical purpose and its relationship to the other hashing tools are absent, and with no annotations the safety profile is only partially implied by the no-shell note.

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% across 4 parameters, so the description must compensate. It adds real meaning for two of them — "argv tokens" clarifies that arguments is a token array not a shell string, and "use relative paths" clarifies working_directory semantics — but says nothing about stdin or the engagement_id format.

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 verb and resource ("Run hashpump from the WebSex forensics toolkit"), which is accurate at the wrapper level, but never explains what hashpump actually accomplishes (hash length-extension attacks). With siblings like websex_hashcat, websex_john and websex_hash_identifier, an agent cannot infer the distinct purpose from this text alone.

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, when-not-to-use, or alternative-tool guidance. The only scoping information is environmental (engagement namespace, relative paths), which does not tell the agent when this tool is the right choice over the other hashing/cracking siblings.

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