kali_password_hydra_brute

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

With no annotations provided, the description carries full burden and does well by disclosing critical behavioral traits: it's a brute-force attack tool (destructive by nature), requires authorization, supports parallel connections (implied by 'parallelized'), and provides protocol specifics. However, it doesn't mention rate limits, error handling, or output format.

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 efficiently structured with clear sections (overview, supported services, warning, example), uses bold formatting effectively, and every sentence adds value without redundancy. The example is particularly helpful for understanding practical usage.

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 complex 10-parameter brute-force tool with no annotations or output schema, the description provides good context about what the tool does, authorization requirements, and protocol support. However, it lacks information about return values, error conditions, and how results are presented to the 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?

With 100% schema description coverage, the baseline is 3. The description adds some value through the example showing parameter usage patterns (target, service, username, password_list), but doesn't provide additional semantic context beyond what's already documented in the comprehensive 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 clearly states the tool's purpose as a 'parallelized login cracker' and 'network login brute-forcer' with specific protocol support, distinguishing it from sibling password tools like hashcat_crack and john_crack which focus on offline hash cracking rather than network login attacks.

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 clear context with the authorization warning and example usage, but doesn't explicitly state when to choose this tool over alternatives like kali_password_hashcat_crack or kali_password_john_crack for different attack scenarios.

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