websex_gau

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 gau is executed directly with argv tokens and that shell parsing is never used, and it notes the engagement namespace context. However, it omits permissions, network behavior, output format details, rate limits, and failure 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 three short sentences, front-loads the command name, and contains no obvious filler. It is appropriately compact for a command-wrapper tool, though the opening sentence could be more informative.

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 four-parameter command wrapper with no annotations and 0% schema description coverage, the description is incomplete. It covers execution mode and path context but leaves stdin, argument semantics, and tool-selection context unexplained. An output schema exists, so return values need not be described, but the input-side gaps remain significant.

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 carry parameter meaning. It clarifies that arguments are argv tokens and that working directories should be relative to engagement artifacts, but it does not explain the stdin parameter or give argument syntax examples. Three of four parameters receive only indirect or no semantic help.

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 essentially restates the tool name: 'Run gau from the WebSex web toolkit.' It does not say what gau does or how it differs from sibling command wrappers such as websex_execute or websex_bash. The remaining sentences describe execution mechanics, not purpose.

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, no when-not-to-use guidance, and no named alternative. The only usage-related note is about namespace and relative paths, which does not help an agent decide when this tool should be selected.

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