websex_hakrawler

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

With no annotations, the description carries the full behavioral burden, and it does add genuinely useful context: arguments are passed as raw argv tokens with no shell parsing, and execution is scoped to the selected engagement namespace. It still omits whether the tool makes outbound network requests, typical target/output behavior, or any rate/timeout characteristics.

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 with the action first and no filler; every sentence carries information. Structure could be improved by leading with functional purpose rather than the runner mechanics.

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 passthrough argv executor the agent needs to know hakrawler's own CLI semantics, which are absent. Combined with zero annotation coverage, zero parameter-description coverage, and no sibling differentiation, the definition leaves significant gaps for correct invocation.

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 coverage is 0% across 4 parameters, so the description must compensate. It meaningfully clarifies 'arguments' (raw argv tokens, no shell) and hints at 'working_directory' via 'use relative paths', but 'engagement_id' is only obliquely referenced as 'the selected engagement namespace' and 'stdin' is never mentioned at all.

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 a specific verb and named binary ('Run hakrawler'), so an agent that already knows hakrawler understands it. However, it never explains what the tool actually does functionally (crawl a target for URLs/JS endpoints), so it does not distinguish itself from the many crawling/URL-gathering siblings (katana, gau, urlfinder, feroxbuster). The purpose is opaque to any agent unfamiliar with the CLI by name.

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 gives working-directory conventions ('relative paths for engagement artifacts') but no guidance about when to choose hakrawler over sibling crawlers, what input it expects first, or any exclusions. An agent is left to infer usage entirely from the bare tool name.

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