gobuster_s3

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

With no annotations, the description carries the full burden. It discloses that the tool performs wordlist-based brute forcing and executes on a remote Kali host via SSH. However, it does not mention whether the scan is read-only, potential rate limits, authentication needs, or any side effects. While 'discovers open S3 buckets' suggests non-destructive reconnaissance, more operational transparency would be expected for a network scanning tool.

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 two sentences, front-loaded with the core purpose and execution context. Every word earns its place, with no redundant or marketing language.

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?

Given the tool's moderate complexity (5 params, no output schema), the description covers the main purpose and execution environment but omits details about expected output/return values, potential impact of the scan, and how to handle results. The schema covers parameters, but the description alone would not fully prepare an agent for what happens after 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?

The schema description coverage is 100%, so the baseline is 3. The description adds context around the wordlist parameter by mentioning 'wordlist-based brute forcing', but it doesn't clarify parameter syntax, formats, or relationships beyond what the schema already provides. No additional parameter semantics are introduced.

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 clearly states the tool's function: 'Amazon S3 bucket enumeration mode - discovers open S3 buckets using wordlist-based brute forcing.' It identifies both the resource (S3 buckets) and the action (enumeration), and the 'mode' phrasing distinguishes it from sibling gobuster tools.

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 provides clear context for when to use this tool: it is for discovering open S3 buckets via wordlist brute forcing. Though it doesn't name alternative tools explicitly, the 'mode' label implies it is one of several gobuster modes, and the S3-specific terminology sets it apart. No exclusions or when-not-to-use guidance is given.

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