Bug Bounty MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'ultra-fast port scanning' and 'skip nmap integration', which hints at performance and optional behavior, but lacks critical details: whether this is a read-only or destructive operation, permission requirements, rate limits, error handling, or what 'fast port scan results' entail. For a tool with 8 parameters and no annotations, 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 well-structured and appropriately sized. It starts with a clear purpose statement, followed by organized sections for 'Args' and 'Returns'. Each sentence adds value without redundancy. Minor improvements could include integrating the parameter explanations more seamlessly, but overall it's efficient and front-loaded.

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 complexity (8 parameters, no annotations, but an output schema exists), the description is moderately complete. The output schema likely covers return values, so the description doesn't need to detail results. However, for a port scanning tool with many configuration options and no behavioral annotations, it should provide more context on usage scenarios, security implications, or performance trade-offs to be fully adequate.

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 compensate. It lists all 8 parameters with brief explanations (e.g., 'Custom port range (default: all ports)'), adding meaning beyond the schema's titles. However, these explanations are minimal and don't cover nuances like format for 'ports' or implications of 'ulimit'. The description provides basic semantics but doesn't fully address the coverage gap.

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: 'Execute RustScan for ultra-fast port scanning.' This specifies the verb ('execute'), the resource ('RustScan'), and the action ('port scanning') with a distinguishing characteristic ('ultra-fast'). However, it doesn't explicitly differentiate from sibling tools like 'masscan_high_speed' or 'nmap_scan' that also perform port scanning, which prevents a perfect score.

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 no guidance on when to use this tool versus alternatives. With multiple sibling tools for scanning (e.g., 'masscan_high_speed', 'nmap_scan', 'nmap_advanced_scan'), there's no indication of RustScan's specific use cases, strengths, or limitations compared to these options. The description only states what it does, not when it's appropriate.

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