race_test

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

The description discloses the core behavior: sending N concurrent requests to the same URL and comparing status codes, response lengths, and success/failure. However, with no annotations provided, it does not mention potential side effects of concurrent requests (especially against mutating endpoints) or any rate-limit/safety considerations.

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 primary purpose and followed by a concise explanation of the detection mechanism. No repetition of schema fields or wasted words.

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 8-parameter schema at 100% coverage and an output schema that can describe return values, the description adequately explains what the tool does and how it detects race conditions. It lacks explicit side-effect warnings and usage guidance, but the core selection and invocation context is sufficiently complete for an agent.

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 100%, so the baseline is 3. The description adds useful context around 'url' and 'concurrency' by explaining that requests are sent concurrently to the same URL, but it does not clarify target_id, scope_include/scope_exclude, or header/body behavior beyond the schema.

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 opens with a specific verb+resource ('Test for race conditions') and clearly explains the mechanism: sending concurrent requests and comparing responses for differential behavior. This uniquely distinguishes it from sibling security scanners such as sqli_scan, xss_scan, and idor_fuzz.

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 intended use case—race condition/TOCTOU detection—is implied by the description, but there are no explicit statements about when to choose this over http_send, http_get, or other scanners. No exclusions or alternative tool references are provided.

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