security.test_auth_bypass

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Test for authentication bypass vulnerabilities' implies this performs potentially intrusive security testing, but doesn't specify whether it's passive or active, what permissions are needed, what side effects it might have, or what the output looks like. For a security testing tool with zero annotation coverage, this is insufficient.

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, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for what it communicates, though it could benefit from additional context.

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 security testing tool with 2 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool actually does (how it tests), what results to expect, or provide enough context for safe and effective use. The agent would need to guess about the tool's behavior and output.

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 50% (only the 'url' parameter has a description). The tool description doesn't mention any parameters or provide additional context about what the 'method' parameter means in the context of authentication bypass testing. The description doesn't compensate for the 50% coverage gap, so it meets the baseline but doesn't add value.

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 'Test for authentication bypass vulnerabilities' states the general purpose (testing for a specific security vulnerability) but lacks specificity about what resource or system it acts upon. It doesn't distinguish from sibling tools like security.test_csp or security.test_xss beyond the vulnerability type.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites, target contexts, or when other security testing tools might be more appropriate. It simply states what the tool does without usage context.

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