gobuster_list_scans

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

With no annotations, the description carries the full burden of disclosing behavior. 'List' implies a read-only operation, and there are no side effects mentioned, which is appropriate for a simple list tool. However, it does not explicitly state whether authentication is required or what constitutes 'recent', leaving some ambiguity about the tool's 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 a single sentence that directly states the tool's function without any filler words. It is front-loaded with the verb 'List' and the resource, making it immediately clear and concise.

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 zero-parameter tool with no output schema, the description adequately states what the tool does. It includes the key qualifiers 'active and recent' to set expectations. However, it does not describe the output format or fields, which could be valuable given the lack of an output schema.

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 tool has zero parameters, and the schema is empty with 100% coverage. Per the rubric, 0 parameters gives a baseline of 4, and the description correctly implies that no parameters are needed. There is no additional parameter meaning to convey.

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 purpose: 'List all active and recent gobuster scans' – a specific verb ('List') and resource ('gobuster scans') with a clear scope ('active and recent'). This distinguishes it from sibling tools like gobuster_status (which checks a specific scan) and gobuster_stop (which stops scans).

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 implies when to use this tool (to get an overview of active and recent scans) but provides no explicit guidance on when to use it versus alternatives like gobuster_status or gobuster_stop. It is left to the agent to infer the tool's role from the sibling names.

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