dirb_scan

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

No annotations are provided, so the description should fully disclose behavior. It mentions execution timing and timeout handling, but does not describe what the tool returns (output schema exists but not referenced), whether it is destructive or read-only, or any side effects. The description partially addresses timing behavior but is incomplete.

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 relatively short, but it is not front-loaded with the main purpose. The first sentence does not convey what the tool does; it immediately dives into execution timing. While concise in word count, it lacks effective structure for quick understanding.

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 8 parameters, no annotations, and an output schema that is not described, the description is severely incomplete. It fails to explain the core functionality, main parameters, and output format. Only timing aspects are covered, leaving the agent without necessary context to use the tool correctly.

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 explain parameters. It only covers timing-related parameters (expected_runtime_seconds, timeout_seconds, etc.) and on_timeout. It does not explain the required 'url', 'wordlist', or 'additional_args'. Thus, significant parameter meaning is missing.

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 does not explicitly state that dirb_scan performs web directory brute-forcing. It assumes the agent knows what 'dirb' is, which is not guaranteed. The name alone is insufficient, and the description focuses on execution timing rather than core functionality.

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?

No guidance is provided on when to use dirb_scan versus sibling tools like gobuster_scan or nikto_scan. The description only advises on timeout strategies, not on the appropriate scenarios for this tool compared to alternatives.

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